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

Annotations already cover read-only/idempotent/non-destructive, so the description correctly spends its words on payload behavior instead: the `recentRuns` window is bounded to 30 days, and the `ai`/`limitPlacesTaken` sub-structures are explained semantically. It does not mention pagination, permissions, or whether the node graph can be large — minor gaps against an otherwise rich disclosure.

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, but the body is one dense paragraph of nested parentheticals ('`failed`, `skipped` when the AI chose not to reply in public, `escalated`') that is hard to scan. Behind a missing output schema most of this detail earns its place, yet the structure could be broken into distinct sentences per payload section.

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?

With no output schema, the description is the only place return values can be explained, and it does that thoroughly for runs, AI steps, and limit places. What remains missing is small: the `flowId` source, and whether the node graph is returned in full or truncated.

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?

There is only one parameter, `flowId`, and schema description coverage is 0%, so the description could have compensated by noting where a flow id comes from or its format. It does not mention `flowId` at all, leaving the schema to carry it. With a single obvious identifier the impact is limited, but the gap is real.

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 opening clause 'Detail of a flow, including its node graph' tells an agent this returns a single flow's full detail, and the sibling set (list_automations, update_automation, get_automation_usage) makes the singular/detail role distinguishable. It lacks an explicit verb ('retrieve'), but the resource and scope are unambiguous.

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?

One genuine usage cue is present — 'the first thing to read when `totalRuns` does not go up' — which frames this as a diagnostic tool. However, there is no explicit statement of when to use this versus list_automations or get_automation_usage, and no prerequisites or exclusions.

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