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

With no annotations, the description carries the burden and delivers real behavior: inclusion criteria (at least two independent sources), lifecycle coverage from first report through recall, fine, lawsuit or settlement, and the return shape (case summaries with permanent URLs). It omits ordering, pagination behavior beyond the schema default, and any auth or rate-limit context, keeping it out of the top band.

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?

Two sentences, scope and verification rule front-loaded, routing hint last where the agent needs it after understanding the result. The parenthetical robot-type list is slightly long but earns its place by defining coverage.

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?

All seven parameters are optional and fully documented in the schema, and the description states what comes back plus where to go for depth, so an agent can call it correctly. Missing only secondary details such as result ordering or whether results are paginated beyond the limit parameter.

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 description coverage is 100% with three enums documented, so the baseline is 3. The description only implicitly maps to the stage filter by enumerating the lifecycle stages, and adds no format or combination guidance beyond the schema.

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?

Opens with a specific verb and resource ("Search verified incidents involving commercial robots and autonomous vehicles") and constrains scope with the two-independent-source verification rule. It also names the sibling it is not (get_case), so an agent can distinguish search from detail lookup without opening either schema.

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?

Explicitly routes the agent to get_case when the timeline and sources are needed, which is the main ambiguity for a search/detail pair. It does not state exclusions or contrast with other siblings like search_nhtsa_sgo, so it stops short of full when/when-not guidance.

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