Pause an Evergreen queue

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description goes beyond them by disclosing exactly what is destroyed: pending occurrences generated by the queue are unscheduled, not just the queue state flipped. It stops short of saying whether already-scheduled runs are cancelled or how state can be restored.

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?

A single front-loaded sentence with no filler; the primary action and its consequence are both present and 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 one-parameter mutation with annotations covering the safety profile and no output schema, the description supplies the key missing behavioral detail (pending occurrences are unscheduled). The remaining gap is the undocumented required queueId.

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?

There is a single required parameter (queueId) with 0% schema description coverage, so the description carries the full burden of clarifying it. The description never identifies queueId, its format, or how to obtain it (e.g. from list_evergreen_queues), leaving a real gap for a required input.

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 (pause) and resource (an Evergreen queue), and adds the side effect of unscheduling pending occurrences, which distinguishes it from a bare 'pause'. It does not explicitly name the obvious counterpart (resume_evergreen_queue / activate_evergreen_queue), so it falls short of a 5.

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?

Usage is implied by the action: an agent can infer you call this when you want a queue to stop firing. However, there is no explicit statement of when to prefer this over update_evergreen_queue, deactivate/delete, or resume_evergreen_queue, and no prerequisites are given.

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