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

The description contradicts the annotations: idempotentHint is false, yet the description states that adding an agent that is already a member succeeds unchanged, implying idempotent behavior. This is a direct conflict between structured metadata and free-text behavior.

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, action first, with no wasted words. The phrase 'on a team that changes its automations without revisions' is slightly awkward and costs a point, but the structure is otherwise efficient.

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, the description covers the action, context, a precondition, and duplicate-member behavior. It is incomplete because it does not explain the outcome when the agent already belongs to another automation, and the idempotency contradiction leaves the agent with conflicting guidance.

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 both agent_id and automation_id described as UUIDs. The description adds no parameter-level detail beyond the schema, so the baseline score of 3 is appropriate.

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 action: add an agent to an automation. It also hints at the distinguishing context of automations changed without revisions, which separates it from revision-based sibling tools, though it does not name an alternative explicitly.

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 this is for non-revision automation workflows and gives a precondition about the agent not belonging to another automation. However, it does not explicitly say when to prefer this over setAutomationRevisionAgent/removeAutomationAgent or what to do if the precondition is violated.

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