fda_device_recalls

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds context about the RES system and offers field examples, but does not disclose return format, pagination, or rate limits; however, for a simple search tool this is acceptable.

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?

Description is brief, front-loaded with purpose, and uses examples efficiently. No wasted words.

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?

With no output schema, the description provides enough context to use the tool: dataset, query examples, and limit behavior in schema. It could mention return fields or default sorting, but is complete enough for a simple search tool.

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?

Both parameters have descriptions in the schema (100% coverage), and the description adds domain-specific examples (pacemaker, software) that illustrate the search syntax. This augmentation helps the agent formulate correct queries beyond the generic OpenFDA examples.

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 function: 'Search FDA medical device recall reports (RES system)' with a specific verb and resource. It further specifies searchable dimensions (name, manufacturer, reason) and distinguishes from sibling tools like fda_device_events by focusing on recalls.

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 clear search contexts via example queries (e.g., 'openfda.device_name:"pacemaker"') and identifies fields for recall searches. It does not explicitly mention when not to use this tool or point to alternatives such as fda_device_enforcement, but the domain and examples make usage clear.

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