describe_capabilities

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool outputs usage guidance, but does not state that it is a safe, read-only introspection call, what the response format is, or whether there are any side effects. For a simple describe-style tool this is a modest gap, but the lack of explicit behavioral detail prevents a higher score.

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 a single, front-loaded sentence with no filler. Every word contributes: it names the action ('describe') and the content ('when this server should be used and how to invoke it'). For a zero-parameter tool, this is appropriately sized and well-structured.

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?

Given the low complexity (0 params, no annotations, no output schema), the description is largely complete: an agent can invoke the tool with no arguments and know it will receive guidance about server usage and invocation. The only minor omission is explicit information about the response format, but this is not critical for such a simple introspection tool.

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 an empty input schema, so the schema already exhaustively documents the invocation surface. Baseline for zero params is 4. The description adds no parameter-specific meaning, but none is needed; there is no conflict or omission to penalize.

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?

The description states a clear verb and resource: 'Describe when this server should be used and how to invoke it.' It distinguishes the tool from the sibling conversion tools by focusing on server-level guidance rather than individual conversion operations. It is not a pure tautology because it adds the content scope (when/how to use the server), though it slightly undersells 'capabilities' by narrowing to usage/invocation.

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?

The description explains what the tool will convey (when the server should be used) but provides no explicit guidance on when an agent should call this tool versus its siblings. There are no alternatives named, no exclusions, and no conditions for selection. Usage is only implied by the tool's name and general purpose.

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