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

Adds real behavioral context beyond the annotations: preconditions (no existing automation membership), immutability of revision bindings, and the re-add-succeeds-unchanged outcome, which is a useful edge case. It does not state error behavior, required permissions, or side effects beyond membership.

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?

Purpose and scope are front-loaded in the first clause, and every sentence carries substantive content (preconditions, immutability, idempotent-like outcome). However, the em-dash-heavy, run-on phrasing makes it denser than necessary and slightly harder to scan.

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 annotations covering safety hints and no output schema, the description covers the important edge cases and preconditions. Remaining gaps (permission requirements, failure modes) are minor for a tool of this complexity.

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% for the two UUID parameters, so the schema already carries the full parameter documentation. The description refers to agents and automations conceptually but adds no format, lookup, or constraint detail beyond the schema.

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 (agent to an automation) with scope qualifiers (team on the Automations workspace). It also distinguishes itself from revision-scoped siblings by explicitly stating 'membership is not versioned', contrasting with tools like setAutomationRevisionAgent.

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?

Gives clear preconditions: the agent must not already belong to another automation, and on revision-based teams it cannot be moved between automations. It does not name an explicit alternative tool (e.g., setAutomationRevisionAgent) for the revision case, so routing is inferred rather than stated.

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