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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds that this is a portfolio-wide aggregate rather than a filtered listing, but says nothing about data freshness, scope (account/workspace), or why open-world access matters. Adequate with annotations, but not rich.

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, zero filler, with the what-it-returns content front-loaded before the routing advice. Every clause earns its place.

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?

An output schema exists, so return-value structure needn't be explained, and annotations cover read-only safety. For a zero-required-parameter read tool this is nearly complete; only the scope of 'your portfolio' (account vs. workspace) and freshness expectations are left unstated.

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 single filter parameter has full schema description coverage including the enum values and the default, so the schema does the heavy lifting. The description's facet list mirrors the enum values without adding format or behavioral nuance beyond them. Baseline 3 applies.

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 (get) and resource (shipment/container portfolio summary) and enumerates the exact facets returned: total active, exceptions, arriving soon, demurrage risk. This distinguishes it from sibling detail tools like get_container_detail and the focused report tools such as get_demurrage_report.

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?

"Use this as the starting point for any shipment question" gives clear context for when to reach for this tool first. It stops short of naming alternatives or stating when-not to use it (e.g. when a single container's detail is needed, use get_container_detail), so it is clear but not exhaustive.

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