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

With no annotations provided, the description carries full burden. It only mentions 'Hazards, manufacturers, remedies' without detailing output format, pagination, rate limits, or side effects. The tool's behavior remains largely opaque.

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 very concise at one sentence and a keyword list, but the list 'Hazards, manufacturers, remedies' is not a complete sentence and could be clearer. It is front-loaded with the action.

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 and no annotations, the description is incomplete. It fails to specify return format, default behavior, or error handling. For a simple search tool, more detail is needed for an agent to use it confidently.

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 minimal meaning beyond the schema. 'Query' is described as 'Product search', which is vague; the tool description does not clarify expected input format. The phrase 'Hazards, manufacturers, remedies' hints at results but does not directly enrich parameter semantics.

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 explicitly states 'Search CPSC consumer product recalls via saferproducts.gov', clearly identifying the resource and source. It distinguishes from siblings like drug_recalls and food_recall_check by specifying 'consumer product recalls', making the tool's domain unique.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for CPSC recalls, but lacks direct comparisons or exclusions. The context of sibling tools provides some implicit differentiation, but the description itself does not offer clear usage guidelines.

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