wait_for_execution

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

Annotations indicate readOnlyHint=true, and description adds non-obvious behavior: timeout is best-effort, poll intervals may cause slight overrun. No contradiction.

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?

Four sentences, no wasted words, front-loaded with the main purpose and then details.

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?

Covers behavior, timeout specifics, queue mode integration. No output schema, but describes return flag. Could mention that it returns the execution object or status, but overall sufficient.

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 has full coverage, description adds nuance for timeoutSeconds ('best-effort') and pollSeconds (interval for checks). Also explains the early return behavior with waiting=true.

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 the specific action ('poll an execution'), the resources it waits for (execution id, terminal states), and includes a special case (Wait node pause). Clearly distinguishes from siblings like get_execution and list_executions which are snapshots, not polling.

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?

Explicitly mentions use after run_webhook in queue mode. Describes conditions like 'returns early with waiting=true' on Wait node. Could add more explicit when-not-to-use or alternative tools, but provides clear context.

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