Get shipment

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds value by detailing the specific data returned (cargo summary, calendar, budget, updates), providing behavioral context beyond the annotations. No contradictions noted.

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?

The description is a single, clear sentence with no extraneous information. It is efficiently front-loaded with the core purpose.

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 that this is a simple get operation with no output schema, the description adequately summarizes what is returned. However, it could mention that logs and cargo are optional via parameters, which would improve completeness for agents configuring calls.

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%, so the description bears the burden of explaining parameters. However, it does not mention any parameter (e.g., what 'logLimit' or 'includeLogs' control). The parameter names are self-evident, but the description should at least clarify how they affect the returned data.

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?

Description explicitly states the action ('Get one shipment') and specifies the included data ('cargo summary, calendar entries, budget summary, and recent updates'). It clearly distinguishes from sibling tools like 'limu_list_shipments' (which lists multiple) and other get tools focusing on subsets.

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?

While it is implied that this tool is used when detailed information about a specific shipment is needed, the description does not explicitly state when to use it over alternatives or provide exclusions. No guidance is given for context selection.

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