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 adds the default sort direction, the field set returned, and the underlying GET /orders endpoint. What it omits is pagination behavior (limit/offset/next_offset chaining) for a list endpoint that can return large result sets.

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?

Three tight sentences, front-loaded with the verb, default order and returned fields, then filters, then the alternative tool. No filler and the endpoint is appended last where it does no harm.

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 an 18-parameter, no-required-parameter list tool with no output schema, the description covers what is returned, how to filter, and where to go for detail records. The remaining gaps are pagination expectations and differentiation from sellasist_search_orders, both of which matter given the parameter count.

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 coverage is 100%, so every parameter including limit, offset, from_id, currency, shipment_id and payment_status is already documented in the schema. The description only names a subset of filter fields and adds no format or semantics beyond what the schema states, 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?

States a specific verb and resource ("List orders") and enumerates what the reply contains (status, billing address, payment, total, source, comment) plus default ordering (newest first). It explicitly routes line items/shipments to sellasist_get_order, so an agent can separate it from that sibling without opening either schema.

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?

It names the concrete filter axes (status, email, name, external id, payment, source, date) and gives an explicit alternative with its condition: "Use sellasist_get_order for line items and shipments." However, it never distinguishes this tool from sellasist_search_orders, which is the closest competing sibling for a list/filter workload.

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