orders_list

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions the key behaviors: listing with filters and pagination. However, it does not explicitly state that this is a read-only operation, describe the response structure, or mention potential limitations like default sort order or rate limits. It is adequate but not thorough.

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, front-loaded sentence that clearly states the purpose. It contains no unnecessary words or repetition, earning every word's place.

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?

Given the tool's complexity (11 parameters, no output schema, no annotations), the description is minimally adequate. It covers purpose, filters, and pagination but does not explain the return format, sorting, or how to interpret the response. While the schema fills parameter gaps, the lack of output schema and annotations leaves room for more detail.

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?

All 11 parameters have descriptions in the schema, so schema coverage is 100%. The description adds no parameter-specific details beyond the generic phrase 'filtros avanzados.' Since the schema already documents each parameter, the baseline of 3 is appropriate.

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 uses a specific verb ('Lista') and resource ('órdenes') and distinguishes this from sibling tools like orders_get and orders_timeline by mentioning 'filtros avanzados' and 'paginación.' It clearly communicates that this is the list/filter operation for 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?

The description provides clear context for when to use this tool: when you need to list orders with filters and pagination. It does not explicitly name alternatives or exclusions, but the context is sufficient to differentiate it from order-specific tools like orders_get and orders_create.

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