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

With annotations already declaring readOnlyHint, idempotentHint, and destructiveHint false, the description adds useful behavioral context by specifying exactly what statuses and insurance categories the tool returns. No contradiction with annotations exists.

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 description is front-loaded with the core purpose, followed by useful return-value detail and example queries. It is slightly long, but each sentence contributes functional guidance and there is no 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?

This is a simple one-parameter read-only lookup with no output schema, and the description explains both the input context and the main return categories. It doesn't cover not-found or error behavior, but for this tool complexity that is not a significant gap.

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?

The schema only defines dot_number as a positive integer with no property description. The description adds some context by indicating the tool operates on trucking companies/carriers, but it never explicitly says the dot_number is a USDOT number or how to obtain it, leaving a small semantic gap.

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 uses a clear verb ('Check') against a specific resource ('trucking company') and enumerates concrete outputs: operating authority status, insurance types, bond/surety, and freight eligibility. It doesn't explicitly differentiate from sibling FMCSA tools like fmcsa_carrier_lookup or fmcsa_safety_scores, but the stated scope is specific enough to identify the tool.

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 provides example questions and a 'use this for' directive, so the intended usage context is fairly clear. However, it doesn't mention alternatives or exclusions, and the closing phrase 'or any carrier compliance check' is overbroad since safety-score checks are handled by fmcsa_safety_scores.

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