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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the useful detail that each item carries concurrency limits and current depth, but says nothing about pagination behavior or total-count semantics despite exposing a pageSize parameter. Modest value beyond the annotations.

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 clauses: the action plus payload, then the practical framing. The core purpose is front-loaded and nothing is wasted; the appended endpoint reference is a minor but tolerable addition.

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?

With no output schema, the description does touch on return content (concurrency limits, current depth), which is the key thing an agent needs. Given readOnly annotations cover safety and the single parameter is fully documented, the definition is nearly complete, lacking only pagination/response-shape detail.

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% for the single pageSize parameter (with min/max documented in-schema), so the description need carry no parameter burden. Baseline 3 is appropriate; the description adds no additional meaning to pageSize.

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 task queues') and goes further by naming what each entry contains (concurrency limits, current depth). It implicitly distinguishes itself from the singular trigger_get_queue sibling by being the collection-level read, but it never explicitly contrasts with it.

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?

The clause 'where you look when work is backing up' gives a diagnostic usage context, which is helpful but implied rather than an explicit condition. It never names alternatives such as trigger_get_queue for a single queue or trigger_pause_queue for remediation, so the agent must infer when this is the right call.

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