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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds meaningful context beyond that: data source, scale (~7,000 product codes), result fields, device class semantics, and public-domain provenance. It does not discuss rate limits or pagination behavior, but the annotation coverage lowers the burden.

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?

Four sentences, front-loaded with the main action and scope, followed by return fields, filters, regulatory meaning, and source. Every sentence earns its place; there is no filler or repetition beyond the minor overlap between the class definitions and the pathway explanation.

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 reference lookup with full schema coverage, a rich output schema, and strong annotations, this description is complete: it states the resource, what is returned, how to filter, what the class values mean, and the data source. An agent has enough information to select and invoke the tool correctly.

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 100%, so the baseline is 3. The description adds value beyond the schema by naming the meaningful filter dimensions: device name, product code, device class, and specialty description, and by explaining what class values 1/2/3 mean for regulatory pathways. It does not provide exact field-name syntax for every filter, but the schema already supplies Lucene 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 opens with a specific action and resource: 'Search FDA medical device classification database', then names concrete outputs such as product code, device class, medical specialty, and regulation number. This makes it clearly distinct from sibling tools like 510k clearance, adverse events, and 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?

The description gives clear implied context for classification questions by listing supported filters and explaining regulatory pathways. However, it never explicitly tells the agent when to use this tool versus sibling openFDA device tools such as openfda_devices.clearance.premarket_510k, openfda_devices.safety.adverse_events, or openfda_devices.safety.recalls.

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