wait_for_batch_completion

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

No annotations provided, so description must cover behavior. It discloses polling strategy (exponential backoff, jitter) and termination conditions (completed/failed/partial/timeout). Omits side effects or idempotency, but acceptable for a polling tool.

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?

Single, efficiently structured sentence that front-loads key behaviors and termination conditions. No redundant words.

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 presence of output schema, description covers core polling behavior adequately. Lacks detail on post-timeout handling or concurrent usage, but sufficient for typical 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 no parameter-specific information beyond schema defaults. Parameter names are somewhat self-explanatory, but missing explanation of jitter_factor or timeout behavior reduces utility.

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?

Clearly states the tool polls batch status with exponential backoff and jitter until completed, failed, partial, or timeout. Specific verb ('Poll') and resource ('batch status') distinguish it from sibling 'wait_for_job_completion'.

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?

Description implies usage for monitoring batch completion with retries, but does not explicitly advise against use for single jobs (sibling exists). Lacks when-not-to-use or alternative recommendations.

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