list_sales_orders

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

No annotations are provided, so the description carries the full burden. It discloses nothing about pagination (the skip/count interplay), the hard max of 100 records in the schema, default sort behavior, whether the result is a full page or truncated, or cost/rate characteristics — all relevant for a 17-parameter query tool.

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?

A single efficient sentence with no filler and the core action front-loaded. It is not padded, though it is arguably too terse given the tool's complexity.

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 17-parameter list tool with no annotations and no output schema, the description is insufficient: return shape, pagination semantics, and the meaning of includeCount/include interactions are left entirely to the schema. An agent can call it, but cannot predict the response or pagination behavior from the definition.

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?

Schema description coverage is 100%, so the schema already documents every parameter (skip, sort, status enum, include nesting, date ranges). The description's 'optional filtering' adds no format or syntax detail beyond that, so the baseline 3 applies.

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 states a clear verb+resource ('Search and list sales orders') and notes that filtering is optional. It implicitly distinguishes itself from the singular sibling get_sales_order, but never names an alternative tool or scope boundary, so it stops just short of a 5.

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?

There is no guidance on when to reach for this tool versus get_sales_order, upsert_sales_order, or the various list_* siblings. The only hint is the word 'optional' regarding filtering, which is not a usage condition an agent can act on.

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