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

Annotations already cover readOnly, idempotent, non-destructive, and openWorld, so the bar is lower; the description still adds real value by disclosing the per-carrier verdict scheme, source coverage and failure reporting, and the analytical-aid disclaimer. It doesn't describe rate limits or latency, but the added context is meaningful.

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?

Four sentences, front-loaded with purpose, then returns, then usage, then disclaimer. Each sentence carries distinct information and none is filler.

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?

With no output schema, the description carries the return-value burden and does so fully (per-carrier verdict, coverage, failures, signals, export formats). Parameters are covered by the schema and safety by annotations, so nothing an agent needs to call it correctly is missing.

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%, and both parameters are fully documented there ('1-10 USDOT numbers,' format enum with default). The description merely restates the 10-carrier cap and the format options, adding no syntax or format detail 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?

States a specific verb (Vet), resource (batch of up to 10 US motor carriers by USDOT number), and outcome (GO/CAUTION/NO-GO). The 'batch' and 'in one workflow call' framing implicitly distinguishes it from single-carrier siblings like carrier_vetting_score, but no sibling is named explicitly.

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?

Gives clear usage context: 'screen a broker's candidate list or lane roster,' plus a useful caveat that each carrier is evaluated independently so one failure doesn't hide others. It does not name an alternative tool or state explicit when-not-to-use conditions, so it stops short of a 5.

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