calculate_paper_weight_and_shipping

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

No annotations are provided, so the description carries the full burden. The ream definition (500 sheets) and the freight CBM output add genuine domain context, but the description never states that this is a pure, deterministic, side-effect-free computation, nor that the tare allowance is opt-in via a parameter. For a read-only calculator the risk surface is low, but disclosure is still thin.

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?

A single efficient sentence that front-loads the calculation and enumerates outputs in a natural progression from unit weight to shipment freight. No filler, though the long compound output list makes it slightly dense.

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?

There is no output schema, but the description effectively enumerates the four return values, which is the most important gap to fill. Combined with 100% schema coverage on the five inputs, an agent has enough to call it correctly; only unit-assumption and determinism disclosures are 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%: gsm, sheet dimensions, quantity, and the include_carton_tare default are all documented in the schema with examples. The description adds only the ream=500 framing and the CBM output, so baseline 3 is appropriate.

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 names a specific verb (Calculates) and enumerates the exact outputs: single sheet weight, ream (500 sheets) weight, total production shipment weight, and freight CBM. This clearly separates it from calculator siblings like calculate_book_spine_width or convert_paper_units, though it never explicitly names an alternative or boundary.

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 phrase 'for paper runs' implies the context of use, and the output list implies it is the tool for weight/freight estimation. However, there is no explicit when-to-use, when-not-to-use, or routing guidance against the three sibling calculators (e.g. when to prefer convert_paper_units instead).

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