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

With no annotations provided, the description carries the burden of behavioral disclosure, and it does that reasonably well: it names the return contents ('due date and status'), enumerates the status vocabulary ('in file, to file, missing, out of date'), and implies a read-only search operation. It does not mention sorting, pagination, or exact match behavior, but these are minor for a straightforward search tool.

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 compact sentences convey the search criteria and the returned data. Every phrase earns its place and there is no redundancy.

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 single-parameter search tool with a well-documented schema, the description covers what the tool searches and what it returns. It lacks explicit guidance on when to prefer this over the sibling report/summary tools, but the core usage context is sufficiently complete.

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%, so the schema already fully documents the single query parameter, including case-insensitivity and shorthand support. The tool description adds no additional parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 action ('Search'), the resource ('driver qualification file items'), and the available search criteria ('driver name or item type'). It also describes the output (matching records with due date and status), making the tool's purpose unambiguous. However, it doesn't explicitly differentiate itself from sibling tools like export_dq_report or list_audit_risks, so it falls just short of a 5.

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 when to use it—whenever you need to find DQ items by driver name or item type—but it never explicitly contrasts it with the sibling tools. There's no 'use X instead when...' guidance, so an agent must infer the boundary between this search tool and the reporting/summary siblings. That's adequate but not explicit.

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