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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is fully covered. The description adds one genuinely useful domain fact — that each order writes one collection per topic — but says nothing about pagination behavior, ordering of results, or what a returned order contains.

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 short sentences with no filler, and the filter is stated up front right after the purpose. The trailing fact about one collection per topic is compact and informative rather than padding.

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 simple read-only list tool with rich annotations, the description covers purpose, filtering, and the meaning of an order. Remaining gaps — pagination defaults and the shape of returned orders (no output schema exists) — are modest but real.

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 0%, so the description must carry the load; it does explain that customer_id/customer_uuid are optional filters and that they are alternatives to one another. It completely omits page and per_page, leaving pagination semantics undocumented beyond the schema's default values.

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 AI collection orders') and names the supported filter. It is clearly a list operation, which implicitly separates it from get_collections_order and edit/delete siblings, but it never names those siblings explicitly.

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?

'optionally filtered by customer' implies the retrieval use case, and it signals both customer_id and customer_uuid as acceptable filters. However, it gives no guidance on when to use this list endpoint versus get_collections_order or list_collections, nor whether the two customer identifiers are mutually exclusive or interchangeable.

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