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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds mild behavioral context by explaining that classification Class 1 is most severe and that results can be filtered by date range, but it does not disclose return shape, pagination behavior, or data source limitations beyond what annotations imply.

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 two sentences long and front-loads the core resource before giving filters and use cases. Every clause earns its place: it identifies the domain, lists the main query dimensions, and states practical applications.

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 simple read-only query tool with five optional, fully documented parameters, the description covers the essential purpose, filters, and use cases. It does not explain the return format, but given the read-only annotations and the schema completeness, the absence is a minor gap rather than a blocking issue.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The description's mention of 'device name or recalling manufacturer, classification, or date range' mirrors the schema fields without adding new parameter-level detail beyond what the schema already states.

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 identifies the resource as FDA medical device recalls and specifies the available filters (device name/manufacturer, classification, date range). It distinguishes this tool from sibling recall tools like fda_drug_recalls and fda_food_recalls by the explicit 'medical device' scope, though it does not use a strong action verb such as 'search' or 'list'.

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?

The description gives an intended context ('medical device supply chain monitoring and hospital biomed compliance'), which implies the tool is for medical-device-specific recall queries. It does not explicitly mention alternatives such as fda_drug_recalls or cpsc_recall_search, nor does it state when not to use this tool.

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