Group and Perform Consolidation

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

Annotations already indicate a write operation (readOnlyHint false) and non-destructive (destructiveHint false). The description adds that it combines two operations, but does not disclose side effects, required permissions, or whether the operation is reversible. With annotations covering basic safety, the score is moderate.

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 very concise—one sentence and a bullet—with no extraneous words. It front-loads the purpose effectively.

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 combined grouping and consolidation operation, the description lacks information on return values, prerequisites, or concrete parameter structure. No output schema exists, and the parameter description is minimal. This is insufficient for an AI agent to fully understand the tool's behavior and inputs.

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 describes 'options' as an object with no specified properties. The description adds example keys (companyId, carrierId, grouping rules), which provides some semantic guidance, but the parameter remains open and under-specified. With high schema coverage (100%), baseline is 3.

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 groups and consolidates consignments in a single operation, combining two steps. This distinguishes it from siblings like group_consignments_for_consolidation and perform_consolidation.

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 implies usage by stating it combines grouping and performing, but does not explicitly state when to use this combined tool versus calling the two separate steps. No exclusion criteria or alternatives are listed.

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