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

With no annotations, the description carries the full burden and does so generously: it discloses that the tool never bills or requires payment, that it deliberately withholds member-identifying fields (USDOT, legal name, link type, hash), that unknown USDOT numbers produce a not_found error, and it flags the ~6% artifact rate in confidence_caveat plus the per-carrier nature of match_score_practical_ceiling.

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 core purpose and the paid-triage routing are front-loaded well, but the middle paragraph is meta-rationale about the 'discovery/sales motion in an agent-only channel' and repeats that it never bills and never requires payment. That rationale is padding an agent does not need to invoke the tool, diluting an otherwise efficient definition.

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?

There is no output schema and no annotations, yet the description qualitatively covers the return surface (flagged boolean, cluster size, linked-carrier count, confidence_caveat, practical match ceiling) and the failure mode, which is what an agent needs before calling. Only the exact response shape and field naming remain unstated, which is a minor gap for a one-parameter screen.

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 0% for the single usdot_number parameter, and the description adds only indirect semantics: that the value is a USDOT number and that an unknown one yields not_found. It conveys the error behavior but no format, validity, or source guidance for the identifier.

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 states a specific verb+resource ('free triage screen for a carrier') and enumerates exactly what it returns: FMCSA chameleon-carrier flag, identity cluster size, and count of linked carriers with a motive. It explicitly positions itself against the sibling check_carrier_identity (paid, member detail), so an agent can route 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?

It clearly frames itself as the free first-step triage and names the alternative ('Call check_carrier_identity (paid) for that'), giving an explicit condition that selects the paid sibling. It stops short of stating when this screen is unnecessary or inappropriate (e.g., carriers already known to be clean), so it is clear context without full exclusions.

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