Update Despatch Dates for Manifest

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

Annotations indicate non-read-only, non-destructive, non-idempotent. The description adds that it updates dates and ETAs but does not disclose side effects, partial update behavior, or whether it returns updated consignments.

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: one for purpose, one for args. No unnecessary words, front-loaded with key action.

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, so return values are not described. Lacks details on date format, error handling, or prerequisites. However, for a simple update tool, the description is minimally adequate.

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 description explains that the 'updates' array contains objects with consignmentId and new despatch date/ETA, adding meaningful context beyond the schema's generic description. Schema coverage is 100%, but the description clarifies the structure.

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 clearly states the verb 'Updates' and the resource 'despatch dates and estimated time of arrival (ETA) for a set of consignments'. It distinguishes from sibling tools which are mostly for getting, creating, or deleting consignments or other entities.

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 description mentions 'for a set of consignments' but provides no explicit guidance on when to use this tool versus alternatives like update_consignment_statuses or update_reprice_consignment. The title hints at manifest context, but the description does not clarify.

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