wait_task

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that expiry returns a snapshot and does not cancel work, but 'separate budget' is unexplained and there is no mention of blocking behavior, permissions, or side effects.

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?

It is a single efficient sentence with the key safety point front-loaded. The phrase 'separate budget' is cryptic, but the overall structure is compact and has no wasted sentences.

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?

For a two-parameter task-waiting tool with no annotations and no output schema, the description is thin. It omits task_id semantics, timeout behavior, what the snapshot contains, and how this differs from sibling tools.

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%, so the description must explain both parameters. It never mentions task_id, and 'expiry' only loosely implies timeout_seconds without explaining its relation to the default or snapshot behavior.

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 verb 'Wait' is clear, and the description adds behavioral detail ('expiry returns a snapshot', 'never cancels work'), but it never states the resource explicitly or says it waits for task completion. 'Separate budget' and 'snapshot' are undefined, and no sibling tool is distinguished.

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 gives no guidance on when to choose wait_task over check_task, get_result, or cancel_task. It implies a safe wait through 'never cancels work', but does not say when waiting is preferable to polling or fetching results.

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