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

Beyond the readOnly/destructive annotations, it discloses that reading is free, sends no messages, returns publish blockers in the dashboard's own wording, and returns steps in the exact shape flows_set_steps accepts. These are behavioral facts an agent cannot infer from the annotations or schema.

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?

Front-loads what the tool returns before moving to usage rules, and every sentence carries routing or safety information. It is on the longer side, but nothing is filler or restated from the name/title.

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?

There is no output schema, so the description carries the burden of explaining the return value, which it does thoroughly (contents, publish blockers, compatibility with flows_set_steps). Combined with the explicit pre-mutation workflow rule, an agent has everything needed to call it correctly.

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 coverage is 100% and the single flowId parameter is already documented in the schema with its source (flows_list or flows_create). The description adds no additional syntax or format detail 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?

Names a specific verb (reads) and resource (one DM flow) and enumerates exactly what is returned: steps, their joins, name, live status, the connected Instagram account, and re-trigger behavior. This is clearly distinguishable from flows_list, which enumerates flows rather than reading one in full.

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 must-do rule ('ALWAYS call this before flows_set_steps on a flow that already has steps') with the reason (flows_set_steps replaces the whole flow, so unread content is deleted). It also names concrete user intents ('what does my flow say', 'why can I not publish this', quoting wording) that select this tool over siblings.

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