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

With no annotations provided, the description must disclose behavioral traits. It only mentions 'search' suggests a read operation, but fails to elaborate on idempotency, side effects, or any constraints. The lack of detail on expected behavior (e.g., pagination, number of results) leaves significant gaps.

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 a single, well-structured sentence that immediately conveys the core functionality. Every word serves a purpose, avoiding unnecessary detail while remaining clear. It is front-loaded and perfectly concise.

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 no output schema, the description partially addresses return values with 'Campaign numbers, defect descriptions,' but this is vague. The tool's simplicity is offset by the lack of behavioral context (e.g., rate limits, data freshness). Overall, it covers the basics without being comprehensive.

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 coverage is 100% with clear parameter descriptions (e.g., '17-char VIN', 'e.g. Toyota'). The tool description adds 'by make, model, or VIN' which mirrors the schema, and 'Campaign numbers, defect descriptions' hints at output but not parameter semantics. Since the schema is already informative, the description adds marginal value, meeting the baseline.

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 NHTSA vehicle recalls by make, model, or VIN.' It identifies the specific resource (NHTSA vehicle recalls) and the action (search), but it could better distinguish from sibling tools like product_recalls or drug_recalls by emphasizing vehicle specificity.

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 offers no guidance on when to use this tool versus alternatives such as product_recalls or drug_recalls. There is no mention of prerequisites, limitations, or preferred search strategies, leaving the AI agent without context for selection.

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