fda_device_classification

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

The annotations declare readOnlyHint=true, so the agent knows it's a safe read operation. The description adds behavioral details about return format (device class, product codes, definitions) and count fields, which are beyond schema. No contradictory or missing critical behaviors.

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 concise, uses bullet points for examples, and is front-loaded with the tool's purpose. Every sentence adds value, and there is no redundancy or verbosity.

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?

Given the absence of an output schema, the description adequately explains the return values and provides count field examples. It covers the main use case well, though could optionally mention error handling or pagination. Nonetheless, it is complete enough for an agent to invoke 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?

The schema description coverage is 100%, but the description adds significant value by providing domain-specific example queries and explaining count fields. This enriches the parameter semantics beyond the schema's generic description of 'search query' and 'limit'.

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 purpose: 'Search medical device classification'. It specifies the resource (medical device classification) and the action (search). Among numerous sibling FDA tools, this one is distinct in focusing on classification details, and the description reinforces that with specific output mentions.

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 provides example queries and mentions count fields, which gives strong usage guidance. However, it does not explicitly differentiate from similar FDA device tools like fda_device_510k or fda_device_pma, nor does it state when not to use this tool. Still, the examples are enough for most use cases.

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