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

Annotations already declare readOnly/no-destructive, but the description goes well beyond by disclosing the response envelope, the fact that a trigger firing with no output produces a TRIGGER CHECK rather than a run, and the cost of includeTriggerChecks ('two extra API calls'). That is exactly the non-obvious behavioral context an agent cannot get from structured fields.

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 return shape, then the critical caveat, then the takeaway. Dense but every sentence carries a distinct point; the capitalized IMPORTANT and the closing restatement of the 'nothing ran vs trigger failing' distinction are slightly redundant.

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 still covers the returned fields, the trigger-check edge case, and the cost tradeoff of an optional parameter — enough for an agent to call it correctly and interpret the result without guessing.

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%, so baseline is 3, but the description adds real meaning for includeTriggerChecks (checks are always reported when there are no runs, and the flag only matters when runs DO exist) and clarifies that time bounds apply to checks as well as runs. It says nothing about top/pagination semantics beyond the schema, keeping it from a 5.

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 and resource ('fetch run history for a flow directly from Power Automate') and immediately enumerates the return shape (runs, runCount, triggerChecks). The 'live' / 'directly from Power Automate' framing implicitly separates it from the store_* siblings, so an agent can select it without opening the schema.

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 explicit interpretive guidance: when there are no runs, or when includeTriggerChecks is set, trigger check history is reported, and the agent is told to read triggerChecks.byStatus before concluding a flow is healthy. It does not, however, name when to prefer it over siblings like get_live_flow_run_error or get_store_flow_runs, so routing between related diagnostic tools is still left to inference.

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