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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the description's job is to add context, and it does: it enumerates the report's contents (coverage/failures, TTW vs WTT totals, intensity, data quality shares, DAF adjustments) and states the dual Markdown + structured return. It does not mention the 100/10,000 shipment limits or key requirements, but the schema carries those.

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 verb and the report's scope, then a compact closing sentence on return format. The middle enumeration is long but each item is a real report section, so it earns its place rather than padding.

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?

No output schema exists, so the description must convey return values, and it does by listing the report sections and the two output formats. The remaining gap is operational context (limits, credentials) which is deferred to the schema rather than the description.

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 schema already documents all 8 parameters including nested shipment/leg structure, and the description adds no parameter-level detail. Baseline 3 applies when structured fields do the heavy lifting.

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 verb and resource ('Calculates shipments and returns a report') and the title pins the scope to many shipments, so it is distinguishable from the singular calculate_shipment sibling. It stops short of explicitly naming which sibling to prefer, but the aggregate-report framing is unambiguous.

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?

There is no statement of when to use this tool versus calculate_shipment or calculate_shipments, and no exclusions or prerequisites (e.g. API key, dataset requirements) are surfaced in the description. Usage is only weakly implied by the word 'report'.

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