wait_for_run

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

No annotations are provided, so the description must fully disclose behavior. It mentions polling and timeout but lacks details on polling interval, terminal statuses, default behavior, error handling, and precedence between runId and target.

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 a single efficient sentence (14 words) that is front-loaded with the purpose. However, it sacrifices necessary detail, making it somewhat under-specified.

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 4 parameters, a nested object, and polling behavior, the description lacks critical details: how to specify run, default polling interval, terminal statuses, timeout behavior, and return value. It is insufficient for proper 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?

With 0% schema description coverage, the description adds minimal meaning: it links 'latest run' to target and 'specific run' to runId, but does not explain pollIntervalSeconds, timeoutSeconds, or the target's envId and flowId fields.

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 the tool polls a run until terminal status or timeout, using specific verbs 'poll' and 'wait', and distinguishes from siblings like get_run (one-time fetch) and get_latest_run (single fetch).

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 description implies usage for waiting on completion, but does not explicitly state when to use this tool versus alternatives like get_run or get_latest_run. No exclusion or comparison is provided.

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