Read one flow run

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

With no annotations, the description carries the burden. It says 'Read-only' which is useful, but does not disclose error behavior, authentication requirements beyond the cryptic 'Uses the Power Automate service (cs_login scope flow)', or what happens if the run is not found. It also mentions 'Unverified against a live tenant' which is honest but does not add operational transparency.

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 description is concise and front-loads the essential purpose ('One run of a cloud flow with its status, timing, trigger and error'). The additional notes on read-only and service usage add value without bloat. It could be slightly more structured but is appropriately sized.

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?

Given the tool has 6 parameters (2 required), no output schema, and no annotations, the description is somewhat spare. It tells the agent what the tool returns conceptually but not the structure or error cases. However, the schema is detailed on parameter defaults, which partially compensates. It is minimally adequate but not complete for robust use.

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 baseline is 3. The description adds value by linking parameters to their source (e.g., runId from cs_list_flow_runs, flowId from cs_list_flows) and explaining default resolution for optional parameters (clientId, tenantId, workspace, environmentId), which helps the agent understand how to fill them without guessing.

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 clearly states it reads a single flow run and lists its key aspects (status, timing, trigger, error). It is distinct from cs_list_flow_runs (which lists runs) and cs_get_flow (which gets a flow definition), though it does not explicitly differentiate from siblings.

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?

No guidance on when to use this tool versus alternatives. It does not mention that cs_list_flow_runs is the precursor to obtain runId, nor does it state when to prefer this over other flow-related tools. The 'Read-only' note is implicit usage context but not explicit routing.

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