Pause managed queue

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

Annotations indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the key behavioral detail that queued messages are retained until resumed, which is valuable beyond annotations. No contradictions.

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?

Single sentence, 12 words, front-loaded with the action verb. Every word is necessary and no extraneous information.

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 pause tool with one parameter, the description covers the key behavior (jobs stopped, messages retained). No output schema exists, but the description is adequate for understanding the tool's effect. Could mention reversibility via resume, but not essential.

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 coverage is 100% (instance parameter described as 'Instance ID.'). The description adds no further detail about the parameter, resulting in baseline score for high coverage.

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 clearly states the tool pauses the queue ('Stop dispatching jobs to the queue's workers') and explicitly notes messages are retained, distinguishing it from sibling tools like 'resume_managed_queue' and 'purge_managed_queue'.

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 description implies usage to pause a queue and hints at resumption ('until resumed'), but does not explicitly clarify when to use this tool vs alternatives like 'purge_managed_queue' or 'set_default_managed_queue'.

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