tool_info

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

Annotations are absent, so the description carries the burden. It mentions 'live --help' and 'whether it mutates state', but does not explicitly state whether tool_info itself has side effects or is read-only. The instruction 'Use before run_tool' hints it's safe, but not explicitly confirmed, leaving some ambiguity.

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 concise sentences that list what the tool provides and when to use it. No unnecessary words or redundancy.

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 no output schema, the description explains the return content (description, examples, help, mutation status) and the intended usage context. It is complete for a retrieval tool without needing error details.

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?

Only one parameter 'name' with a clear description and example ('openapi_diff.py'). The schema covers 100% and the example enhances understanding, so it's above baseline.

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 clearly states the tool's purpose: to provide full detail about a single tool, including description, example commands, live --help, and mutation status. This distinguishes it from siblings like find_tools (discovery), run_tool (execution), and list_categories (categorization).

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 says 'Use before run_tool', giving a clear directive on when to call this tool. It also implies it's for retrieving details about a specific tool, contrasting with find_tools for searching and list_categories for listing categories.

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