get_order

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

No annotations are provided, so the description carries the full burden. The word 'Obtenir' implies a read-only operation, and the description adds what details are returned (lines, status, deliveries). It does not explicitly state side-effect-free behavior, permissions, or error cases, but for a simple getter, this is minimally sufficient.

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, concise sentence with the verb and object front-loaded. Every word earns its place, listing the key return elements without unnecessary elaboration.

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 getter with one parameter and no output schema, the description is complete: it states the action, the resource, and the types of information included. It gives an agent enough context to select this tool confidently, even without formal annotations.

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 covers 100% of the parameter (id) with its own description, so the baseline is 3. The tool description does not add any additional semantic meaning to the id parameter, but none is needed since the schema alone is clear.

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 'Obtenir' (get) and the resource 'une commande client' (a customer order), with specific detail on what is included (lignes, statut, livraisons). This distinguishes it from siblings like get_supplier_order (supplier orders) and list_orders (listing), making the purpose 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?

The description provides clear context: use this tool to retrieve complete details of a customer order. The word 'client' implicitly excludes supplier orders, and the detail list (lines, status, deliveries) indicates it is for full-order retrieval. However, it does not explicitly mention alternatives or when not to use it, but the scope is clear enough.

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