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

Annotations already establish readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the bar is lower. The description adds useful behavioral context: coverage since 1976, 58,000+ records, returned recall fields, and the source database. No contradiction with 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 well structured and front-loaded: it opens with the core action and scope, then adds return fields, filter syntax, and provenance. The 'Essential for...' clause is mildly promotional but still provides useful selection context.

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, optional-parameter search tool with an output schema, this is nearly complete: it covers dataset scope, filters, Lucene syntax, return payload highlights, source, and use cases. The only small gap is that 'date' filtering is mentioned without an exact field name, though the example fields cover the main use cases.

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%, so the baseline is 3. The description adds meaning beyond the schema by mapping the generic search parameter to specific fields (device_name, recall_status) and demonstrating Lucene syntax with 'or'. Skip and limit are left to the schema, which fully documents them.

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 an explicit action ('Search') on a concrete resource ('FDA medical device recall records'), scopes it by dataset size and time range, and lists the return fields. It distinguishes itself from sibling tools like fda_openfda.safety.drug_recalls or vehicle.safety.recalls by naming medical devices and the FDA CFRES source.

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 when-to-use guidance via stated filterable fields, Lucene syntax examples, and use cases such as 'medical device safety research, regulatory compliance, and patient risk assessment.' It does not explicitly name sibling alternatives or state when not to use it, but the context is strong enough for an agent to select it correctly.

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