wait_for_build

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

No annotations, but description fully discloses non-polling behavior, immediate return, and what happens on terminal state (full details and artifact URLs). No side effects mentioned, but not needed for read-only check.

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, front-loaded with purpose, no wasted words, efficient and clear.

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 simple check tool with no output schema, description explains return content and usage pattern. Could mention error handling for invalid build_id, but overall complete given low complexity.

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?

Only one parameter 'build_id'; schema already describes it as 'The Codemagic build ID to check'. Description adds minimal context beyond schema. With 100% schema coverage, baseline 3 is appropriate.

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 it checks the current status of a Codemagic build, distinct from siblings like 'get_build' and 'cancel_build'.

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 it returns immediately and requires repeated calls with the same build_id; provides expected time range (10–40 minutes) and frequency (20+ times normal). Lacks explicit alternatives but context is clear.

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