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

Annotations already indicate non-read-only (mutating) and non-destructive behavior. The description adds minimal behavioral context beyond stating it generates a chart. No mention of credit consumption or potential side effects.

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 concise with four front-loaded sentences, no redundancy, and clearly states purpose, prerequisites, and usage context.

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?

The description covers main purpose and prerequisites but lacks details about output format, return value, or potential execution time. Given no output schema, mentioning the output type (e.g., chart format) would improve completeness.

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%, but the description adds value by providing examples for target_name ('Samsung Galaxy S25', '5G NR Release 17') and emphasizing the requirement for a prior search_id.

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 specifies a clear verb ('Generate'), resource ('AI Hit Chart'), and context ('for a specific target from a previous search'). It effectively distinguishes from siblings like claimhit_search and claimhit_get_result.

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?

The description explicitly states when to use the tool ('when the user asks to chart, map claims, or analyse a specific target in detail') and notes required prerequisites (search_id, target_name). However, it does not mention when not to use or provide alternatives.

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