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

With no annotations, the description carries the full burden and delivers: it discloses paid flat pricing, that registry_unavailable calls are not billed, that unknown USDOT numbers return a free not_found, the hashing/verification protocol (record_hash is SHA-256, verify_url confirms issuance), and what is deliberately excluded (safety_tier_derived). This is unusually rich behavioral disclosure for a tool with zero annotation coverage.

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 lead sentence front-loads what the tool is and its price, and the sentences are dense with distinct information. It is long, but almost every clause conveys contents, integrity, or billing facts rather than restating fields; the enumeration is verbose but mostly earns its place.

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, no-output-schema tool, the description is complete: it catalogs the returned sections (profile, SMS, crash summary, changes, identity triage, insurance continuity, authority events, review_factors), explains integrity verification, and states billing edge cases. An agent has everything needed to call and interpret it.

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?

There is one parameter with 0% schema description coverage. The description implies usdot_number identifies the carrier and that an unknown value yields a free not_found, but it never states the expected format (e.g., the bare integer form versus a USDOT prefix), so it only partially compensates for the empty 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?

The opening sentence states a specific verb+resource: a dated, hashed record of a carrier's public FMCSA data built for a broker's vetting file. It explicitly distinguishes itself from scoring tools ('It is a record, not a score') and enumerates the exact contents, so an agent can separate it from siblings like get_safety_history or check_carrier_identity.

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 context 'built for a broker's carrier-vetting file' implies the use case, and 'Paid, flat price' warns about cost. However, it never states when to choose this comprehensive record over narrower siblings such as get_safety_history, get_inspection_crash_summary, or lookup_carrier, nor any exclusion conditions.

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