experimental-ext-tool-annot.../docs/next-spec-iteration-priorities.md
Sam Morrow 2c6eb7f686
docs: outline next specification priorities
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 3ce9ad35-1e45-451f-98f6-802946669ba8
2026-08-12 09:16:06 +02:00

1.4 KiB

Priorities for the Next Specification Iteration

This is a non-binding summary of where the Tool Annotations Interest Group believes its attention would be most useful next. The IG has no formal remit to set the MCP roadmap or determine the disposition of SEPs; these priorities are intended to focus discussion, implementation, and feedback.

1. Mature Existing Extension Work

Complete the transition of existing SEP proposals into fully fledged experimental extensions. Each extension should have SDK implementations and clear evidence that the community wants and will use it before it is proposed for graduation.

2. Prepare Pre-flight Requests for Review

Bring the pre-flight request proposal (SEP-1862) to a state where it is ready for substantive review. This remains a core protocol proposal rather than an experimental extension.

3. Separate Human and Agent Content Presentation

Explore how content intended for human formatting and display can be represented separately from content intended for agents. The goal is to let clients provide good human-facing experiences without compromising the structured content agents need.

4. Evaluate Annotation Proposals

Gather the proposed annotation SEPs, evaluate how they relate to one another and to the extension work, and provide consolidated feedback to their authors and reviewers.