fda_drug_recalls

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

Annotations confirm readOnlyHint=true, consistent with description. Description adds context about classification seriousness (Class I=most serious) and the openFDA query syntax. No contradictions, though no mention of rate limits or pagination.

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 extremely concise: one sentence for purpose, then bulleted examples. Front-loaded with the most important info, no filler. Perfect for an agent to quickly grasp and use.

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, the description adequately informs the agent what results to expect (recall reports). It covers search fields, example queries, and limit parameter, making it complete for execution.

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 description adding value through concrete examples for the 'search' parameter (e.g., 'classification:"Class I"') and clarifying 'limit' defaults and max. The description transforms generic schema into actionable patterns.

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's purpose: 'Search FDA drug recall enforcement reports.' It specifies the verb (search/find) and resource (FDA drug recall enforcement reports), and distinguishes from siblings by focusing on recalls specifically.

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?

Provides example searches that illustrate how to use the tool effectively. While it doesn't explicitly tell when to use over alternatives, the examples offer practical guidance for query construction. Lacks explicit when-not-to-use or comparison with similar tools.

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