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

Annotations declare readOnlyHint=true, so the tool is a read-only lookup. The description adds that pricing is done 'through real quotes with bookable quote ids' but does not state that the tool itself is non-destructive. It adds important context including the behavior for unconsolidatable loads (they come back with a reason) and how to handle trucks priced above LTLs (shown with recommended:false; don't hide). The description also notes 'Auth optional — works keyless like the quote tools.' This is valuable behavioral context beyond annotations. However, it does not specify whether the returned quote IDs are always valid or if they expire, which would be useful transparency. Score 4 because it adds significant behavioral detail beyond the readOnlyHint.

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 a single dense paragraph that packs in purpose, usage guidelines, behavioral notes, and next steps without wasted words. It is front-loaded: the first sentence defines core functionality completely. Every subsequent sentence adds new information: clustering criteria, pricing logic, use cases, failure reasons, honesty policies, next action, and auth requirements. It is concise yet comprehensive.

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?

Given the tool has 2 parameters, 100% schema coverage, no output schema, and no nested objects, the description is remarkably complete. It explains the entire workflow: clustering logic, pricing comparison, recommended flag behavior, failure reasons, and the action path (call book). The description even relays expected agent behavior ('relay reasons honestly' and 'don't hide' recommended:false trucks). For a tool without an output schema, the description compensates thoroughly by describing what will be returned and how to handle it. Context signals indicate low complexity, and the description fully addresses all gaps.

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 100%, so the schema already documents all parameters and their descriptions. The description adds semantic value by explaining how parameters are used in the overall consolidation logic: 'clusters loads sharing an origin+destination zip whose pickup dates fall within window_days (default 3) that together fit one 53' dry van.' It also gives a default value for window_days (3). This clarifies the role of parameters beyond the schema descriptions. The description explains what the loads array represents and the criteria for clustering. Score 4 because it adds meaningful usage context while schema already has good parameter descriptions.

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 clearly states the tool finds consolidation savings across 2-12 upcoming loads by clustering loads sharing origin+destination zip and pickup date window that fit one 53' dry van, then pricing each cluster both ways (combined FTL vs sum of LTLs) through real quotes with bookable quote IDs. This provides a specific verb (find/find consolidation savings) and resource (loads), and distinguishes it from sibling tools which are individual quote/booking tools.

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 explicitly states when to use: 'Use when the user has several loads to ship this week, asks if anything can ride together, or wants to cut freight spend.' It also tells when not to keep hidden: 'A truck pricing above its LTLs is shown with recommended:false; don't hide it.' It provides next-step action: 'To act on a proposal, call `book` with the consolidated truck's quote_id.' It also gives instructions for handling failures: 'Loads that can't consolidate come back with the reason... relay reasons honestly.'

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