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

The readOnlyHint annotation already indicates this is a safe read operation, and the description is consistent with that. The description adds that it returns 'all' available specs and that the title is the distinguishing field, but it does not disclose return format, ordering, or other behavioral traits. This is adequate given the annotation coverage but not enriched.

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 two short sentences, with the primary action stated first. The second sentence adds a practical usage hint without redundancy. Every word earns its place; no fluff or unnecessary detail.

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 tool's simplicity (zero parameters, no output schema, read-only operation), the description is sufficiently complete. It states what is listed (all OpenAPI specs) and how to use the result (select by title). No additional context is necessary for an AI agent to understand and invoke this tool correctly.

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, so the description is not required to explain parameter semantics. Baseline for zero parameters is 4. The comment about selecting a spec by title hints at the output shape rather than input parameters, which is acceptable since there are no parameters to document.

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 uses a specific verb ('Lists') and resource ('all available OpenAPI specs'), making the tool's function immediately clear. It also distinguishes itself from sibling tools like list-endpoints (endpoints vs. specs) and get-endpoint (single endpoint retrieval). The added directive 'Use the title to select a spec' reinforces the purpose.

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 usage context is implied rather than explicit: the tool lists all specs so a user can choose one by title. However, there is no explicit statement about when to prefer this over sibling tools, nor any when-not-to-use guidance. This places it at the 'implied usage' level.

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