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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful domain context and deprecation warnings, but it does not describe listing behavior, return format, or pagination.

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 front-loaded with the core resource definition, then immediately clarifies the two common confusions: webhooks and campaign sequences. Every sentence earns its place by preventing a likely wrong tool selection.

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 zero-parameter, read-only list tool with rich annotations and no output schema, the description is largely complete: it defines scope and steers away from deprecated webhook tools and campaign-flow tools. It could mention the shape of returned automation objects, but that absence is minor given the tool's low 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?

The tool has zero input parameters, so there are no parameter semantics to explain. Per the zero-parameter baseline, a 4 is appropriate; the description does not need to compensate for parameter documentation.

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 defines the resource precisely as account-level event-driven workflows outside any single campaign, and explicitly distinguishes it from campaign sequences handled by `flow_get`/`flow_set`. It does not directly state the listing action, but the tool name and title make that clear, and the scope is well differentiated from siblings.

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?

It gives explicit exclusions and alternatives: webhook tools are deprecated and should not be looked for, while campaign sequences belong to `flow_get`/`flow_set`. This routes the agent away from wrong siblings, though it does not state prerequisites or when to prefer `automation_get` after listing.

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