Wait for a deploy to finish

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

The description explains polling until terminal state or timeout, defaults to most recent deploy. Annotations indicate readOnlyHint, idempotentHint, destructiveHint: false, and the description adds behavioral details without contradiction.

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?

Two sentences, no fluff. Each sentence provides essential information: first describes polling behavior and terminal states, second gives usage guidance.

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, but the description mentions terminal states and timeout, implying return of deploy state. Minor gap: does not explicitly state that the current deploy object is returned.

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%, so baseline is 3. The description adds value by explaining the default for deployId ('Defaults to the service's most recent deploy') and the intended usage pattern.

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 verb 'polls a deploy' and the resource 'deploy'. It lists terminal states and distinguishes from sibling tool render_retrieve_deploy by recommending its use instead of manual polling.

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 'Use after render_create_deploy instead of polling render_retrieve_deploy in a loop.' This gives clear context for when to use and what alternative to avoid.

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