gov.fda-recalls

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

With no annotations, the description should disclose all behavioral traits. It mentions ordering (newest first) and filtering capability, but omits details like data freshness, pagination, rate limits, or whether results are limited. This is insufficient for a tool with no 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?

The description is a single sentence that front-loads the core purpose and key filters. No wasted words, but could benefit from structured bullet points for clarity.

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 does not mention output format or any metadata like data source, update frequency, or default limit. With no output schema and 4 parameters, the description is too minimal for complete understanding.

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 lists three of four parameters (drug, classification, status) but does not explain the 'limit' parameter or provide input format details for 'drug'. The schema has 0% description coverage, so the description partially compensates but still lacks full 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 clearly states the tool lists FDA drug recall enforcement reports sorted by newest first, and mentions filtering by drug name, classification, and status. However, it does not differentiate from sibling FDA tools like gov.fda-drug-events or gov.fda-device-events.

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 alternatives, nor any prerequisites or exclusion criteria. The description implies usage for recall data but does not address when not to use it.

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