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

The description says 'Adding a queue that is already a member succeeds unchanged', which describes an idempotent repeat behavior, but the annotations set idempotentHint=false. This is a direct contradiction. The description also does not disclose what happens when the queue already belongs to another automation, which is the most important failure behavior for this operation.

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?

The description is short and contains three sentences, but the first sentence's phrasing 'on a team that changes its automations without revisions' is confusing and does not earn its place. The second and third sentences are useful behavioral constraints, but the overall structure lacks clarity and flow.

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 two-parameter mutation tool, the description covers the core operation and one repeat-behavior nuance. However, it omits error outcomes for the uniqueness violation, any permissions or prerequisites, and a clear statement of the affected automation type. It is minimally viable but leaves important gaps.

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%, with both parameters having at least basic descriptions like 'Automation ID' and 'Queue ID'. The description adds a uniqueness constraint but does not enrich parameter meaning beyond what the schema already provides. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 verb and resource: 'Add a queue to an automation'. The clarification that the queue must not already belong to another automation adds scope. However, the phrase 'on a team that changes its automations without revisions' is awkward and does not cleanly distinguish this tool from revision-related siblings like setAutomationRevisionQueue.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The 'without revisions' phrase hints that this tool applies to direct automation edits rather than revision-based workflows, but it never names an alternative or states a selection criterion. The constraints about queue membership are behavioral, not usage routing.

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