search_device_classifications

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

Without annotations, the description carries full burden. It adds context about class risk levels but does not disclose pagination behavior (skip/limit), result ordering, error handling, or any response format details. The description provides basic functionality but not deeper behavioral traits.

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 with no wasted words. The first sentence immediately states the purpose and the second adds helpful risk classification context. It is front-loaded and efficient for an AI agent to parse.

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 7 optional parameters, no output schema, and no annotations, the description lacks information on how multiple search criteria interact, what the output structure looks like, and pagination behavior. It covers the basic search intent but leaves gaps that could affect agent usage.

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 already describes all 7 parameters with clear descriptions (100% coverage). The description merely lists the fields without adding new meaning, examples, or constraints beyond what the schema provides. The class risk explanation is also present in the schema's deviceClass description, so no additional value.

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 searches the FDA medical device classification database and lists specific searchable fields (name, class, specialty, product code, regulation number). It explains the risk levels for classes. The name and sibling tools (e.g., search_device_510k) make the distinct purpose obvious.

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 implies usage for classification lookups by specifying the database and fields, but it does not explicitly state when to use this tool over siblings like search_device_recalls or search_device_adverse_events. No exclusion criteria or context-dependent guidance is provided.

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