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 well: it discloses the paid pricing model ('you pay only when a call returns records; an exact-key miss is free'), warns against assuming Active by enumerating carrier_status values, and specifies that match fields return boolean/null rather than the value on file. It also flags a schema change (removed 2026-09-19).

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?

Purpose and pricing are front-loaded, and every paragraph earns its place by conveying matching or return-value behavior. It is on the long side and the dated removal note adds minor bulk, but density of useful detail justifies it.

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 no-annotation, no-output-schema tool with 0% schema coverage, the description supplies pricing behavior, return-field warnings, and full claimed_* semantics. It stops short of describing pagination or the full profile's field list, but the identity-verification path an agent needs is 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 coverage is 0%, so the description must compensate, and it explains the five claimed_* parameters' matching semantics (claimed_name against legal_name OR dba_name; address fields against physical_address; any subset allowed) plus the name_match/physical_address_match return convention. Only usdot_number is left implicit, which is self-evident.

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 and resource ('look up a single carrier's current profile by USDOT number') and pins the scope to one carrier, which distinguishes it from the sibling search_carriers. The agent can tell what it returns and on what key without opening the 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?

Gives a clear condition under which the claimed_* fields should be used (confirming a carrier's claimed identity, e.g. catching double brokering), which is strong contextual guidance. It does not, however, explicitly name or route away from the sibling identity tools (check_carrier_identity, screen_carrier_identity, confirm_identity_link), leaving the agent to infer boundaries.

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