ntsb_aviation_accidents

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

Annotations already declare readOnlyHint=true, which the description aligns with. Beyond that, it discloses specific return content (event details, injuries, aircraft info, probable cause, report status). This adds useful context about what the search yields, though it doesn't cover pagination or output format details.

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?

Three concise sentences front-load the purpose, followed by a brief returns list and three illustrative examples. No fluff—every sentence earns its place.

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 simple search tool with three well-documented parameters and a readOnlyHint, the description covers the core purpose, search criteria, and return fields. It's slightly incomplete in that it doesn't explain pagination (limit/offset) or explicitly differentiate from the similar ntsb_query sibling, but these are minor gaps.

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%, so the baseline is 3. The description's examples ('Boeing 737 MAX', 'Cessna engine failure', 'helicopter New York') echo the schema's own examples and don't add new semantics beyond what's already in the parameter descriptions.

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 'Search NTSB aviation accident investigation data' and 'Find accident reports', using a specific verb and resource. It differentiates from the broader ntsb_query sibling by explicitly narrowing to aviation accidents.

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 context on what to search (aircraft type, location, date, keywords) and provides concrete query examples. It doesn't explicitly mention when not to use this tool or name alternatives like ntsb_query, but the examples imply typical usage.

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