Load one full tool schema

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description still adds real context: it is a lazy-loading primitive that returns schema and annotations rather than executing anything, which tells the agent the call is metadata-only. It does not cover failure behavior for an unknown server/tool name.

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?

Two sentences, zero filler, with the core action front-loaded and the sibling routing placed second. Every clause earns its place.

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 two-parameter read tool with full schema coverage and safety annotations, nothing needed to call it correctly is missing; the description even states what the response contains (schema plus annotations), compensating for the absent output schema.

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?

Schema description coverage is 100%, with both 'server' and 'tool' documented in-schema, including the pointer to list_servers. The description reinforces the one-tool scope but adds no syntax, format, or naming details beyond the schema, so baseline 3 applies.

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 specific verb and resource: fetch the complete JSON schema plus annotations for exactly one upstream tool. The phrase 'exactly ONE' and 'the precise, lazy-loading primitive' separates it from the listing/search siblings (list_tools, search_tools) without needing their schemas.

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?

Explicitly routes between alternatives: use suggest_tools for a vague prompt, use this when the tool is already known. This is a direct when-to-use / when-not-to-use split naming the sibling.

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