explain_tool

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

The description marks the tool as read-only and lists the metadata fields it returns. It also explains the optional includeSchema parameter behavior. No annotations are provided, but the description fully compensates.

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. First sentence details output; second provides usage guidance and read-only flag. No wasted words.

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 adequately lists the metadata fields returned (title, summary, risk level, etc.) and explains the optional schema inclusion. Sufficient for understanding the tool's output.

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 coverage is 100% with descriptions. The description adds context: name accepts aliases, includeSchema defaults false for minimal output, which enhances understanding beyond the schema.

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 expand a single tool's metadata including title, summary, risk level, tags, aliases, etc. It distinguishes from sibling tools like discover_tools by specifying usage context.

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 states when to use: 'Use after discover_tools to understand a specific tool before calling it.' Also notes it is read-only, guiding the agent on safe usage.

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