list_orders

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

Annotations are absent, so the description carries the full burden. It only states the list action and status codes, without disclosing return format, pagination behavior, default limits, or any side effects. This is minimal behavioral context for a list operation.

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 concise and front-loaded with the tool's purpose. However, the status mapping duplicates schema information and introduces a mismatch, making it less clean than necessary.

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?

With 4 parameters, no output schema, and no annotations, the description should explain the return value and filter usage. It does not mention what the tool returns or how sqlfilters work, leaving significant gaps for a list tool.

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 status mapping is repeated but inconsistent: the description says status 2='En cours' while the schema says 'Expédiée'. Page, limit, and sqlfilters are not explained in the description, and schema description coverage is only 25%, so the description fails to compensate for the low coverage.

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 'Lister les commandes clients' (list customer orders), specifying the action (list) and resource (customer orders). This distinguishes it from siblings like get_order (single order) and list_supplier_orders (supplier orders).

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 get_order for a single order or list_invoices for invoices. The status enum hints at filtering but does not explain scenarios or exclusions.

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