search_device_recalls

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

No annotations provided, so description carries burden. Discloses pagination (limit, skip) and counting capability, but does not explicitly state it is read-only or mention any potential side effects, rate limits, or authentication needs. The 'search' parameter hints at FDA API query syntax but does not specify behavior.

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?

Very concise: one-line purpose followed by parameter explanations. No unnecessary text. Front-loaded with purpose, then parameter details.

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?

Output schema exists, so return value documentation is covered externally. Description adequately documents input parameters. Could optionally mention that it is read-only or reference the FDA recall report source, but not strictly necessary.

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 0% according to context, meaning the schema only provides titles and defaults. The description adds essential meaning: explains that 'search' is an openFDA query, 'limit' caps at 1000, 'skip' is for pagination, and 'count' is for field counting. This greatly enhances usability beyond the schema.

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 states 'Search FDA medical device recall enforcement reports', providing a specific verb and resource. It clearly distinguishes from sibling tools like 'search_drug_recalls' and other device searches.

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. Does not mention sibling tools or provide context for when this search is appropriate.

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