wait_for_job

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

No annotations exist, so description carries full burden. It reveals blocking behavior and optional download, but omits edge cases (timeout handling, failure behavior, download destination). Adds some value beyond schema but incomplete.

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 sentence with two clear clauses, front-loaded with main action. No unnecessary words; perfectly concise.

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 tool complexity (4 parameters, blocking, optional download, output schema exists), description is too sparse. It lacks details on timeout behavior, error handling, download specifics, and polling frequency. Insufficient for reliable agent invocation without further context.

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 0% description coverage; the description adds meaning for timeout (max wait), download (optional result retrieval), and interval (polling frequency) implicitly. However, it does not explicitly explain parameter semantics or format, leaving gaps.

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 blocks until a job finishes and optionally downloads results, with a specific verb 'Block' and resource 'job'. It distinguishes from siblings like check_job (non-blocking) and cancel_job.

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 job completion with optional download, but does not explicitly guide when to use vs alternatives like check_job or download_job_result. No clear when-not-to-use or exclusion criteria.

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