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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the semantic role of queues (warehouse/shipping-profile grouping), but says nothing about pagination, result volume, or auth needs; the '[DEMO]' tag is unexplained and adds ambiguity rather than context.

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 compact sentences front-load the core action and filters, with no wasted prose. The trailing '[DEMO]' marker is the only element of unclear value.

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?

Return values are covered by the existing output schema, so the description needn't explain them. For a simple filtered-list tool, what remains is a minor gap around paging and the meaning of the DEMO tag.

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 each of the five filters is already documented in the schema. The description restates the filter names without adding format details (e.g., substring semantics for QueueName, which the schema covers), 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 clear verb+resource ('List order queues') and enumerates the filterable fields, so an agent can tell this is a read/list operation. It doesn't explicitly differentiate from the sibling teapplix_manage_queue, leaving that inference to the agent.

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 implies usage by noting filters are optional and explaining that queues group orders by warehouse and shipping profile, but gives no explicit when-to-use/when-not guidance or pointer to teapplix_manage_queue for creation/modification.

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