Lister les commandes

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

Annotations provide readOnlyHint=true, and the description aligns with this by describing a listing operation. The description adds valuable behavioral context about the two distinct filtering modes (creation date for quotes vs value date for validated orders) and the optional delivery method filter, which goes beyond what annotations provide.

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 efficiently structured in two sentences that pack substantial information: first sentence explains the core functionality with date filtering logic, second adds optional filtering. Every word serves a purpose with zero redundancy.

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 read-only listing tool with no output schema, the description provides comprehensive context about what can be listed, filtering logic, and optional parameters. The main gap is lack of information about return format or pagination, but given the annotations and tool purpose, it's reasonably complete.

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?

With 0% schema description coverage, the description compensates well by explaining the semantics of validatedOrders parameter (distinguishing quotes from validated orders/invoices), date parameters (different date fields used based on order type), and filterDeliveryMethod (delivery mode filtering). It provides meaningful context beyond the bare schema.

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 'list' and resource 'orders', specifying two distinct types (unvalidated quotes vs validated orders/invoices) with different date filtering criteria. It distinguishes this tool from sibling tools like order_detail (detail view) and sale_create (creation).

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 about when to use this tool: for listing orders/quotes within date ranges, with optional delivery method filtering. It doesn't explicitly mention when NOT to use it or name alternatives, but the context is sufficiently clear for proper usage.

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