Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnlyHint, idempotentHint, etc.), the description reveals the full return shape, clarifies the semantic guarantee that all returned repos are 'currently active in the federation registry,' and provides the change-order governance context. With no output schema present, this additional return-structure disclosure is highly valuable and goes beyond what annotations capture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a clean purpose statement but contains redundancy: 'Returns: The set of covered repositories.' repeats the earlier return-shape mention. The example 'call introspection_system_list_repos with arguments {}' is trivially unhelpful, and 'Added by change-order 2026-05-28-003 (Phase 3)' is process noise that dilutes signal, making it slightly less crisp than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only discovery tool with strong annotations, the description is complete: it states what it returns, provides the return structure, highlights the active-registry constraint (a key semantic), and explains how the output should be used. With such low complexity, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and schema coverage is trivially 100%. The description correctly includes an example call with empty arguments, matching the baseline of 4 for parameter-less tools. No parameter-specific insight is needed since none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

'List the ComOS repositories that contribute to introspection' uses a specific verb+resource combination and names the domain (ComOS, introspection). It distinguishes itself from sibling introspection_* tools by explicitly scoping to repositories and positioning itself as a discovery tool for 'introspection_system_climb_history'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance: 'Use this to discover which repo ids to pass to introspection_system_climb_history.' This clearly states the primary consumer of the output and when an agent should call this tool. It lacks an explicit when-not or alternatives list, but the named downstream tool provides strong contextual guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.