Wait for a build to finish processing

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

With readOnlyHint=true already covered by annotations, the description still adds real behavior: it blocks, defaults to a 30-minute wait, polls, and is a Pro feature. It doesn't note what happens on timeout (partial return vs error), which is the one meaningful gap.

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?

Three tight sentences with the core behavior and terminal state front-loaded, then the timeout caveat and the Pro-gating note. No filler.

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?

No output schema exists, and the description implies the terminal state (VALID) but doesn't state what is returned or how a timeout surfaces. For a simple polling tool with full schema coverage, this is nearly complete.

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 coverage is 100% and the schema already documents poll_seconds, max_wait_seconds, defaults and caps. The description only restates the 30-minute default, adding no syntax or semantics beyond the schema, so the baseline 3 applies.

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 a specific verb (poll/wait) and resource (the newest uploaded build), plus the terminal condition (VALID) and the goal (ship flow in one call). This clearly differentiates it from the sibling list_builds.

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 says when to use it (to make the ship flow one call) and when not to (if you should not hold the session that long, call list_builds yourself instead). The alternative is named with the selecting condition.

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