Perform Consolidation

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive behavior. The description adds that merging reduces shipment units but does not detail side effects like state changes to original consignments. No contradiction with annotations.

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 concise with three sentences: purpose, benefit, and parameter list. It is front-loaded and contains no wasted words, earning high marks for efficiency.

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 write operation with a complex object parameter and no output schema, the description lacks essential details such as effects on existing consignments, constraints, error handling, and output format. It is insufficient for correct invocation without external knowledge.

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 description specifies that the 'request' parameter includes consignment IDs and consolidation parameters, adding meaning beyond the schema's generic 'Consolidation request payload'. Schema coverage is 100%, but the description provides useful contextual detail.

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 consolidates consignments into consolidated shipments for carrier efficiency, providing a specific verb and resource. However, it does not differentiate from related sibling tools like machship_group_consignments_for_consolidation, which limits clarity regarding when to use this exact 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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., consignments must be grouped first). It lacks context for proper invocation.

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