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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context beyond annotations: partial-name matching, a 50-result cap, the FMCSA national database source, and the fields returned. It does not discuss zero-result or ambiguous-match behavior, but this is a minor gap for a read-only search.

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 compact and front-loaded: core operation first, return fields second, then matching behavior and examples. The example list is mostly helpful, though 'or any carrier name search' is a slightly redundant catch-all and the 'freight carriers in Texas' example is a bit loose because the tool only searches by company name.

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 appropriately lists the key return fields and the result limit, giving an agent enough information to invoke and interpret the tool. The main gap is that it does not warn that searches are name-only and cannot filter by location, despite one example mentioning Texas.

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 explain the parameter. It does: the 'name' parameter is a company name, partial matches are supported, and examples clarify expected input. It stops short of specifying case sensitivity or formatting, but the schema constraints and examples suffice for this simple one-parameter tool.

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 opens with a specific verb and resource: 'Search for trucking companies... by company name,' then lists concrete returned fields (DOT number, MC number, location, fleet size, operating status). It also notes partial name matching, which helps distinguish it from exact-lookup siblings like fmcsa_carrier_lookup.

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 gives explicit example questions and states 'or any carrier name search,' so an agent knows when to invoke it. It does not explicitly mention when to prefer sibling tools such as exact DOT/MC lookup or safety-score tools, though the name-search framing implies the boundary.

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