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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered externally. The description adds nothing beyond those annotations—no statement of what the output describes, whether it reflects static or runtime state, or any side considerations. With an output schema present the return shape is covered, but the description contributes no behavioral context of its own.

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?

A single front-loaded sentence with no filler. It is perhaps too terse for the ambiguity involved, but as a matter of conciseness there is nothing to cut.

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?

Annotations and an output schema carry most of the load, and there are no parameters to explain, so the description is not dangerously incomplete. Still, for an introspection tool an agent would benefit from knowing it describes the calling agent and when to invoke it, which 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 takes zero parameters, so the baseline of 4 applies. The phrase 'input contract' loosely signals the payload describes inputs, which is consistent with the empty schema.

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?

States a verb and a resource ('Return capabilities and input contract'), so the basic action is inferable. However, 'capabilities' and 'input contract' are abstract and it's never made explicit that this describes the calling agent itself or the server, leaving the object of the description ambiguous. Siblings (certify, green_route, etc.) are unrelated, so there is no differentiation burden, but the purpose is still only vaguely pinned down.

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?

There is no indication of when an agent should call this versus proceeding directly to the sibling tools, and no mention of prerequisites or typical triggers. The agent must guess that this is a discovery/introspection call.

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