Pause the queue

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

The description adds behavioral detail beyond the annotations: processing halts only after the current task finishes, and tasks remain queued. It also references the resume path. The idempotentHint annotation covers repeat-invocation behavior, so the description does not need to restate it.

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?

Three short sentences deliver the core behavior, the state preservation guarantee, and the resume counterpart with no filler. The most important fact, when the pause takes effect, is front-loaded.

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 zero-argument state-change tool, the description is complete: it states what happens, when it happens, and how to undo it. The output schema is absent but not needed for such a simple operation.

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?

The tool has zero parametersasi, so parameter semantics are trivially complete. The baseline for zero-parameter tools is 4, and the description appropriately focuses on behavior rather than parameters.

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 queue processing, with the precise timing detail 'after the current task finishes.' It also clarifies 'Tasks stay queued,' which distinguishes it from a cancel operation. This is specific and immediately understandable.

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 gives clear context for when to use the tool: to pause processing temporarily while retaining queued tasks. It mentions queue_resume as the natural counterpart. However, it does not explicitly contrast with queue_cancel, leaving the main alternative usage boundary implicit rather than fully explicit.

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