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

Annotations already establish readOnly/idempotent/non-destructive, and the description goes beyond them by disclosing the built-in-flow fallback (`builtIn`) when a flow has no emails, the 30-day window on metrics, and the fact that draftFlow overwrites a flow — a strong implicit warning to read first. It omits any statement about result size, ordering of the flows list, or limits.

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 content is dense and every sentence carries information — the flow contents, the fallback rule, the read-before-write rule, the audience precondition. The opening sentence is a long run-on list, and the important audience gate is placed last rather than front-loaded, which slightly weakens scanability.

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 not be re-explained, and the description still covers the meaningful surprises (fallback flow, metric window, precondition). What is missing is minor: whether all flows are returned or paginated, and any ordering or size expectations.

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?

With a single optional parameter at 100% schema description coverage, the schema already explains that workspaceId accepts an id or slug and may be omitted for single-workspace connections. The description adds nothing about the parameter, so the 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?

The description names the resource (every automated email flow) and enumerates exactly what is returned: on/off state, store dependency, ordered emails with wait times and personalization, plus 30-day send/open/click metrics. The `draftFlow` reference makes the boundary between reading and rewriting a flow explicit, so an agent can separate this from siblings without opening a 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?

It gives an explicit sequencing rule ('Read it before draftFlow rewrites a flow') and a hard precondition ('Only for a workspace with subscribed email contacts'), which functions as a when-not condition. It does not address the other adjacent mutators (enableFlow, updateFlowStep), so the alternative routing is only partial.

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