Details d'une livraison / CRA

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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds 'détaillées' (detailed) but doesn't elaborate on possible errors, permissions, or formatting. It does not contradict annotations, and the bar is lowered due to annotations, but it doesn't provide much additional behavioral context.

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?

One succinct sentence that front-loads the purpose and method. No unnecessary words or redundant details.

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 simple get-by-ID tool with one parameter and no output schema, the description is mostly complete. It covers the essential action and resource. However, it could mention what the output consists of (e.g., full delivery details) which is only implied by 'informations détaillées'.

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 input schema already provides a full description of the 'id' parameter (numeric identifier). The tool description merely restates that it's the ID. With 100% schema coverage, the description adds no new semantic value.

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 (Récupère les informations détaillées), the resource (livraison/CRA), and the method (par son ID). It distinguishes from sibling search tools by focusing on single entity retrieval by ID.

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?

Usage guidance is implicit: it's for fetching a specific delivery by ID. However, no explicit when-to-use vs alternatives (e.g., boond_deliveries_search) is provided. The sibling search tool likely handles filtered queries, but this is not stated.

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