Problem
The discovery meta-tools hide most downstream tool metadata:
describe_tool exposes only name, description, and inputSchema (internal/metatools/formatters.go:236-241).list_tools exposes only name and description (internal/metatools/formatters.go:102-119).
Dropped: outputSchema, annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), and title.
Why it matters
Proposal
Add outputSchema, annotations, and title to describe_tool output as additive JSON keys (omitted when the downstream tool does not set them). list_tools stays minimal; the discovery tier is deliberately small.
Problem
The discovery meta-tools hide most downstream tool metadata:
describe_toolexposes onlyname,description, andinputSchema(internal/metatools/formatters.go:236-241).list_toolsexposes onlynameanddescription(internal/metatools/formatters.go:102-119).Dropped:
outputSchema,annotations(readOnlyHint,destructiveHint,idempotentHint,openWorldHint), andtitle.Why it matters
annotations, an agent (or a policy layer in front of it) cannot distinguish a read-only downstream tool from a destructive one.outputSchema, clients have no contract for thestructuredContentthat now flows through since feat: preserve structuredContent from downstream MCP tools #972.Proposal
Add
outputSchema,annotations, andtitletodescribe_tooloutput as additive JSON keys (omitted when the downstream tool does not set them).list_toolsstays minimal; the discovery tier is deliberately small.