search_device_classifications

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

No annotations provided and description only states 'Search' without revealing behavioral traits like idempotency, rate limits, or potential side effects. Since annotations are absent, the description carries the full burden but fails to add behavioral context.

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?

Very concise: one-line header then bulleted parameters. No fluff. Front-loaded with purpose. Could be slightly improved by including defaults or a brief usage example inline.

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?

Adequate for basic use but missing usage context (e.g., which sibling to choose), error handling info, or prerequisites. Output schema exists so return values are covered elsewhere, but the agent would benefit from more guidance on query formatting.

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 has 0% description coverage, but the description's Args section explains each parameter (search, limit, skip, count) with clear semantics and examples, adding significant meaning beyond the raw schema types.

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?

Clearly states 'Search FDA medical device classifications' – a specific verb and resource. Distinguishes from sibling tools like search_drug_ndc or search_device_510k by specifying 'device classifications'.

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 an example query but no explicit advice on when to use this tool vs. siblings (e.g., drug search tools or other device searches). Usage is implied but not guided.

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