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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral detail beyond that — no pagination, result ordering, or rate-limit notes — so it neither contradicts nor meaningfully extends the 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?

Three short sentences with zero filler: identification first, filterable fields second, use-case context last. Every clause earns its place and nothing is buried.

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?

For a read-only, zero-required-parameter query tool with no output schema and annotations covering safety, the description supplies purpose, filters, and use cases adequately. It does not explain return shape or result ordering, but with annotations present and no output schema required, that omission is minor.

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 100%, so every parameter (limit, query, start_date, end_date, classification) is already documented in the schema, including the Class 1 severity note. The description mirrors those facets but adds no syntax or format detail beyond what the schema provides, matching the baseline for full coverage.

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?

States a specific verb/resource pair ('FDA medical device recalls') and immediately enumerates the filterable facets (device name, manufacturer, classification, date range). This clearly distinguishes it from siblings like fda_drug_recalls, fda_food_recalls, and cpsc_recall_search without needing to open any schema.

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?

Names concrete use cases (medical device supply chain monitoring, hospital biomed compliance), which gives an agent clear context for when this tool applies. It stops short of explicit when-not guidance or naming an alternative sibling for overlapping recall queries, so it is not a 5.

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