validate_shipment

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

The parenthetical 'makes it official' hints at a state change, but with no annotations, the description fails to disclose other behavioral aspects such as irreversibility, permissions, or downstream actions.

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 exceptionally brief and front-loaded, with the essential action stated immediately. There is no filler, and every word adds value.

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?

As a mutation tool with no annotations or output schema, the description is too sparse. It does not explain the consequences of validation, what 'official' means in practice, or any additional requirements.

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 'id' parameter is not described in the text, and the schema only says it is a number. With 0% schema description coverage, the description should compensate by explaining what ID to provide, but it does not.

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 action ('Valider une expédition') and adds the effect ('la rend officielle'), which distinguishes it from related tools like deliver_shipment. It is specific and unambiguous.

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 is provided on when to use this tool versus alternatives such as deliver_shipment or other validation tools. The description neither states prerequisites nor excludes any scenarios.

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