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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's contribution beyond that is the returned field list and the existence of the GET /search/orders endpoint; it says nothing about pagination behavior, default result volume, or what happens when filters conflict — though the schema covers limit and the starting_after cursor.

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?

Two sentences, front-loaded with the resource and its return shape, then the filters — no repetition of the title and nothing redundant. The trailing 'GET /search/orders' is the only low-value token, since the agent cannot use endpoint paths directly.

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 12-parameter read-only list tool with no output schema, the description usefully compensates by naming the returned fields (order number, billing name/address, form, total, currency, status), which the agent otherwise could not know. What remains thin is pagination guidance and default page size in prose, though both are fully documented in the schema.

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% across all 12 parameters, and each parameter carries a precise description (including the cursor explanation and enum for sort), so the baseline of 3 applies. The description's parameter prose restates the schema's filter set ('event (form), status, buyer email, customer id, order number or dates') without adding format or edge-case semantics such as date string format.

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+resource ('List orders') and adds real definitional detail: one order per checkout, plus the exact fields returned and the filters available. It does not explicitly name a sibling like ticketspice_get_order as the alternative for a single order, so differentiation is implied by the 'list' framing rather than stated.

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?

Enumerating the filterable dimensions (form, status, email, customer id, order number, dates) implicitly tells the agent when this tool is the right one, and 'newest or oldest first' hints at sort intent. However, there is no explicit when-to-use/when-not, and no pointer to ticketspice_get_order for single-record lookups, which is the most likely confusion given the sibling set.

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