List shipments

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety profile is clear. The description adds no additional behavioral context such as pagination behavior (limit/offset) or filtering logic. It does not contradict annotations, so a 3 is appropriate.

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 sentence directly states the tool's purpose with no wasted words. However, it may be too terse and could benefit from additional details without sacrificing conciseness.

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?

Given the 11 parameters and no output schema, the description is incomplete. It omits pagination details, filtering parameters, return format, and how totals are calculated. The context of many sibling tools also demands more clarity about what makes this tool distinct.

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 0% with 11 undocumented parameters. The description adds no meaning to any parameter; it only mentions 'search' and totals but does not explain how parameters like mode, status, location, or date ranges work. This fails to compensate for the missing schema descriptions.

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 states it searches shipments with calendar, cargo, and package totals, clearly indicating the tool's function. However, 'calendar totals' is somewhat ambiguous and does not differentiate from sibling list tools like limu_list_cargo or limu_list_packages, which also deal with shipments but may lack totals.

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?

No guidance on when to use this tool versus the many sibling list tools. The description does not mention alternatives or context for using this specific search/list tool over others.

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