Get Tool Help

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds behavioral detail: the two modes of operation (param absence vs presence). However, it does not explain other behavioral traits like pagination or error handling, so limited added value beyond annotations.

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 short (three sentences plus example), with purpose and usage front-loaded. However, the example is empty braces (missing param example), and the structure could be improved by listing param roles. Still, no extraneous 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?

Given the tool has 5 parameters with 0% schema coverage and no output schema, the description is incomplete. It only addresses the 'tools' param, leaving significant gaps. The agent cannot properly invoke the tool for tasks like filtering by tool_name or topic without additional documentation.

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 0%, yet the description only explains one parameter ('tools') out of five. Parameters 'only', 'tool_name', 'topic', and 'response_format' are untouched. The description adds minimal meaning beyond the schema, leaving the agent uninformed about critical filtering options.

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: 'Discover available tools and get detailed documentation with JSON schemas.' It distinguishes itself from sibling tools (all data operations) by being a meta-help tool. The verb 'discover' and 'get' with resource 'tool documentation' is specific and unambiguous.

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?

Provides clear usage guidance: 'Call without params to list all tools. Use tools param for full docs + schemas.' Includes an example. Does not explicitly state when not to use, but the purpose is clearly differentiated from siblings, so usage context is implied.

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