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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: best-orientation floor count (not naive length division), the double-stack height condition, and that payload weight decides whether weight or floor binds first. It does not add auth/rate-limit detail, but none is needed for a pure calculator.

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?

Front-loaded with the core question and trigger, then the output shape. The single long paragraph is slightly dense and repeats the pallet/vessel enumerations the schema already carries, but every sentence earns its place in clarifying output behavior.

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 read-only calculator with an output schema, the description fully covers what is computed and why the result differs from naive division, and it routes the agent to the catalog tool for valid vessel values. Nothing needed to invoke it correctly is missing.

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 baseline is 3. The description restates pallet dimensions and vessel examples already present in the schema, and adds that gross weight 'only affects the payload-limited count', which is a marginal gain over the schema wording.

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?

States a specific question the tool answers ('how many pallets fit in a given container/trailer/wagon/ULD') and names the exact resource domain. The concrete examples (20ft holds 11 Euro, 40ft holds 25) make clear this is a solved pallet-loading calculation, distinguishable from calculate_cbm and get_container_dimensions.

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?

Explicitly says 'Use this whenever someone asks how many pallets... fit', giving a clear trigger. It also points to get_container_dimensions for the vessel catalog, but does not explicitly contrast with calculate_cbm or plan_cargo_load, so the sibling routing is only partially covered.

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