how_to_use_forgetful_tool

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

The description implies a read-only operation returning documentation, with no mention of side effects, authentication, or rate limits. It is adequate but not explicit.

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 includes an Args and Returns section that, while structured, contains some redundant phrasing. Could be more concise, but is still reasonably clear.

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 presence of an output schema, the return values need not be detailed. However, the tool is simple (1 param, read-only), so the description is mostly complete, though usage guidance is lacking.

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?

The description explains the single parameter 'tool_name' as 'Name of the tool to get documentation for', which adds meaning beyond the bare schema that lacks a description. Schema coverage is 0%, but the description compensates well.

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 it returns documentation for a specific tool, but does not explicitly distinguish from the sibling 'discover_forgetful_tools' which likely lists all tools.

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?

No guidance on when to use this tool versus its siblings 'discover_forgetful_tools' or 'execute_forgetful_tool'. The agent is left to infer the use case.

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