deliver_shipment

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

No annotations are provided, and the description only states the state change to 'delivered'. It does not disclose whether the shipment must be validated first, whether date_delivery defaults to today, whether the action is reversible, or any permission requirements. For a mutation tool this is a significant gap.

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, front-loaded sentence with no filler words. It is concise, but so terse that it omits useful operational context that could be included without much added length.

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?

For a status-mutation tool with no annotations and no output schema, the description leaves out preconditions, default behaviors, and consequences. It is minimally viable but incomplete for an AI agent to invoke correctly, especially within a workflow of shipment-related tools.

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 schema provides a description for date_delivery but none for id, giving 50% schema coverage. The tool description adds no parameter details at all, failing to compensate for the missing id semantics; the id's meaning is only inferable from the tool name.

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 uses a specific verb ('Marquer') and resource ('expédition'), indicating the action of marking a shipment as delivered. This distinguishes it from sibling tools like create_shipment, validate_shipment, and get_shipment.

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 provides no guidance on when to use this tool versus alternatives such as validate_shipment or create_shipment. It does not mention workflow position, prerequisites, or exclusions; usage is only implied by the verb.

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