enhance_tool_description

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

Discloses internal actions like examining metadata and generating improvements, but no annotations provided to fill gaps. No information on side effects, permissions, or reliability.

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, front-loaded with purpose and usage. No redundant information.

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?

Complete for a documentation tool: explains purpose, usage, and parameter intent. Lacks return value details, but output schema absent; error handling not discussed.

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 covers 100% of parameters with descriptions; the description adds minimal value beyond summarizing (e.g., 'adding examples') that aligns with generate_examples parameter.

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 verb 'analyzes' and resource 'MCP tools', specifying it enhances descriptions. It uniquely stands out among sibling tools which are primarily for configurations, searches, and dashboards.

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?

Directly advises to use when improving tool documentation with examples/clarifications. Lacks explicit when-not-to-use, but context is clear and no similar sibling tools exist.

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