Read one cloud flow

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

No annotations are supplied, so the description carries the transparency load; it declares 'Read-only' and warns that including the definition yields a large payload, which is genuinely useful cost information. It does not cover permission/auth prerequisites or any rate/limits caveats, so it is strong but not exhaustive.

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?

Two compact sentences with the purpose front-loaded, followed immediately by routing guidance. Every clause carries information and nothing is padded or repeated.

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 proactively names the return content (trigger/action names, connection references, definition JSON), which is exactly what an agent needs to consume the result. Combined with the explicit alternative routing, an agent can select and invoke this correctly without opening the schema.

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 the schema already documents all seven parameters including includeDefinition and the auth-related defaults. The description's mention that includeDefinition returns the 'whole Power Automate definition' largely restates what the schema field already says, so it adds little beyond baseline.

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 combination ('Read one cloud flow') and enumerates exactly what comes back: trigger and action names, connection references, and the full definition when requested. It clearly separates itself from the list-oriented sibling cs_list_flows by describing a single flow inspection.

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?

Explicitly routes the agent: use before cs_update_flow, and for diagnosing why a flow cannot be switched on, while directing run-history questions to cs_list_flow_runs and cs_explain_flow_run instead. Both the 'when' and the 'instead use' alternatives are named.

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