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

Annotations already cover read-only and destructive hints (readOnlyHint: false, destructiveHint: false). The description adds context by explaining the output nature ('maps patent claim elements to product features element-by-element with evidence') and the prerequisite of a previous search. However, it does not disclose side effects like credit consumption or result persistence, which are likely relevant given the sibling tools.

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 three sentences: it states the main action, explains what a Hit Chart is, and provides usage context. Every sentence adds value, with no redundancy or irrelevant details. It is front-loaded and efficient.

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 tool has no output schema, so the description should explain what the return value or result of generation is. The description says 'Generate an AI Hit Chart' but does not clarify whether the chart is returned directly, stored for later retrieval (e.g., via claimhit_get_result), or if there are follow-up steps. Given the sibling set includes get_result, this is a notable gap. Still, the description covers the main action, prerequisites, and when-to-use, making it adequate but not fully complete.

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 both parameters well-described. The description adds no new parameter-level details beyond restating that search_id comes from a previous search and target_name is the exact name. Since the schema fully covers the parameters, the baseline of 3 is appropriate.

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 specific action ('Generate') and resource ('AI Hit Chart') for a target from a previous search. It explains what a Hit Chart is (maps claim elements to features), which distinguishes it from sibling tools like search or get_result. The scope is well-defined.

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 says 'Use this when the user asks to chart, map claims, or analyse a specific target in detail,' providing clear when-to-use guidance. It does not explicitly name alternatives, but the context is sufficient for an agent to differentiate it from search or retrieval operations.

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