pack_containers

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

Discloses return format (coordinates, volume utilization, weight, unplaced pieces) and solver used, but does not explain behavioral traits like whether it modifies state, handles special shapes (box/cylinder), or applies stacking/rotation defaults. No annotations to supplement, so description bears full burden.

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?

Two sentences front-loaded with action and result. Every word serves a purpose; 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?

Adequate for a tool with nested parameters and no output schema, but missing details on container vs. containers options, shape handling, and option defaults. Could be more complete given complexity.

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 50% (some fields have descriptions). Description adds output context but does not explain input parameters like shape, includeInLoading, allowStacking, allowRotation, loadingDirection, or container options. Without compensation, this leaves agents uncertain about key inputs.

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?

Clearly states verb 'pack', resource 'cargo SKUs into shipping containers', and solver used ('Kubova solver'). Distinct from siblings (estimate_capacity, generate_report, verify_key) which focus on capacity estimation, reporting, and verification.

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?

Implies usage for packing cargos into containers but does not explicitly state when to use vs. alternatives (e.g., estimate_capacity for capacity checks). No exclusion criteria or prerequisites provided.

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