Read one flow run

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

With no annotations, the description has to carry the load: it does declare read-only and adds a notable caveat that the tool is 'unverified against a live tenant.' It omits what happens on a missing/inaccessible run and whether auth failures surface distinctly, leaving the mutation/error profile partly undocumented.

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-loaded with the returned resource and fields, then the read-only and auth facts, then the reliability caveat. Compact with no filler, though the fragment style ('Read-only. Uses the Power Automate service...') reads terse rather than explanatory.

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?

No output schema exists, and the description compensates by naming the fields returned. Auth scope and the live-tenant caveat cover the main unknowns for a single-record read. Only error/not-found behavior is left unaddressed.

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% and each parameter (runId, flowId, connection/auth defaults) is already documented in the schema, including where ids come from. The description adds no parameter-level semantics of its own, so 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 resource (one flow run) and enumerates the payload an agent gets back: status, timing, trigger and error. 'One run' implicitly contrasts with cs_list_flow_runs, but no sibling is named explicitly, so it stops short of a 5.

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?

The auth precondition is stated ('Uses the Power Automate service, cs_login scope flow'), which is genuine usage context. However, it never says when to pick this over cs_list_flow_runs, cs_explain_flow_run, cs_compare_flow_runs or cs_analyze_flow_health — the closest siblings.

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