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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so mutation semantics are partly covered. The description adds genuinely non-obvious behavior: membership is not versioned, revisions bind immutably, and re-adding an existing member succeeds unchanged — context the annotations cannot convey.

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?

Front-loaded with the core action, then the constraints. It is dense — several ideas packed into two long sentences — but each clause (non-versioned membership, immutability, re-add behavior) carries real information, so little 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 two-parameter mutation with no output schema, the description covers the key calling constraints and edge cases (existing membership, revision-bound queues). It does not describe error/failure modes or required permissions, a minor gap given the annotation coverage.

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% with only two UUID parameters (automation_id, case_queue_id), so the schema already carries the semantics. The description adds no format, source, or constraint detail for the individual parameters, so the documented baseline of 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?

States a specific verb (add) and resource (queue to an automation) plus the constraining scope (team on the Automations workspace, versioned vs. revisioned). This lets an agent distinguish it from setAutomationRevisionQueue / removeAutomationQueue without opening a schema.

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 preconditions (queue must not already belong to another automation; on revision-based teams it cannot be moved between automations) but never names an alternative sibling tool or explicitly says when to prefer setAutomationRevisionQueue over this one. Usage is implied through constraints rather than routed.

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