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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered without the description's help. The description adds a useful domain fact ('Each order writes one article per topic') but says nothing about pagination defaults, result volume, or return shape for a list endpoint with page/per_page controls.

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 tight sentences with zero waste; the core list action and the filtering constraint are front-loaded before the domain note. Nothing needs trimming.

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 read-only list tool with rich annotations and no output schema, the description covers identity and filtering but omits result-set expectations and pagination behavior, which matter given two undocumented paging parameters.

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 carries the full burden, yet it only clarifies that customer_id and customer_uuid are interchangeable customer filters. The page and per_page parameters (with defaults 1 and 50) are never explained, leaving half the parameters semantically bare.

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 opens with a specific verb and resource, 'List AI article orders', and scopes it to optional customer filtering. It implicitly distinguishes itself from singular/destructive siblings (get_articles_order, create_articles_order, delete_articles_order) through the 'List' verb, though it never names those alternatives 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' signals when the filter is relevant, but there is no guidance on when to prefer get_articles_order for a single order, nor any mention of how paging through large result sets should work. Usage is implied rather than stated.

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