get_flow_run

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

No annotations are provided, so the description carries the full burden of behavioral disclosure and largely fails. "Reconcile its terminal state locally" hints at a possible local side effect, but it never clarifies whether the call mutates state, requires auth, or is idempotent — critical ambiguity for a tool described as a "read".

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?

A single front-loaded sentence with no filler, which is appropriately sized for the tool. The second half, however, is opaque enough that its brevity costs clarity rather than buying it.

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 annotations, no output schema, and no parameter documentation, the description is the only source of behavioral context and it supplies almost none. An agent cannot tell what the response contains, what "terminal state" means, or whether calling it has side effects.

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 0% and the description only loosely implies that a template identifier and a run identifier are involved. It adds no meaning about format, where run_id comes from (presumably run_flow_template), or constraints beyond the schema's length limits.

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 names a specific verb and resource ("Read a template run's status"), which is distinguishable from siblings like get_flow_template and run_flow_template. However, the trailing clause "reconcile its terminal state locally" introduces jargon that muddies rather than sharpens the stated purpose.

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?

There is no explicit guidance on when to call this versus alternatives, no mention of calling it after run_flow_template, no polling cadence, and no statement about which run states are terminal. The only hint of usage is the implicit association with template runs.

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