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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine domain context beyond that: a queue posts one item every cadenceHours at timeOfDay in its timezone and keeps `lookahead` items booked at the platform. Return format and pagination behavior are not described, keeping it short of a 5.

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, followed by the behavioral model of a queue; the trailing '(Wraps GET /api/v2/queues.)' is compact provenance. Slightly dense parenthetical could be trimmed but nothing is wasted.

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 single-optional-parameter list tool with no output schema, the description covers what the tool is, what a queue means, and the underlying endpoint. It never states that the return is a collection of queue objects, but that is implied by 'list' and the resource noun.

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% and the sole brandId parameter is fully documented in the schema (personal / brand id / omitted → last active brand, brand-bound key behavior). The description adds nothing about parameters, 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?

The description names the resource precisely – 'Posting (drip) queues of one brand' – and even defines what a queue is, so the domain concept is unambiguous. It does not, however, explicitly position itself against siblings like get_queue, create_queue, or delete_queue; the agent infers 'list' from the title and the plural framing.

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?

There is no explicit when-to-use statement, no prerequisites, and no alternative named (get_queue for a single queue, create_queue for creation). The '[read-only]' tag hints at safe invocation but gives no routing guidance.

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