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

Goes well past the annotations (which only flag readOnly=false, destructive=true, idempotent=true): it discloses the execution identity (runs as the user), a scheduling constraint (outside quiet hours), a negative capability list (never submits a bid, messages a buyer, declines a tender, emails outside the team, or changes workspace membership), and the authorization model (owners, admins, bid leads). No contradiction with destructiveHint — 'acts on the team's pipeline as its rules say' is consistent with a mutating, enabled-side-effect tool.

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?

Four dense sentences, each carrying distinct load: precondition, runtime behavior, capability limits, auth/alternative. The gating precondition is front-loaded in the very first clause, which is exactly where an agent needs it.

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?

An output schema exists, so return values need no explanation, and both parameters are covered by the schema. The description covers everything else an agent needs for a mutating, permission-gated tool: consent gate, execution identity, side-effect boundaries, and auth roles.

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%, so both parameters (workspace, automation) are already documented in the schema. The description reinforces that the automation is referenced after having its rules read back, but adds no new syntax or format guidance beyond what the schema supplies. Baseline 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+resource (turn an automation on) and immediately adds what that means operationally: it runs as the user, outside quiet hours, and acts on the team's pipeline. Explicitly names the sibling it is not (turn_off_automation), so an agent can route correctly without opening either 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?

Gives an explicit precondition ('only after you have read an automation's rules back to the user in plain words and they said yes'), which is a hard gate on when to call it. Also names the exact alternative for the inverse operation (turn_off_automation), covering both when-to-use and when-not-to.

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