appcrane_wait_deploy

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

No annotations, but the description thoroughly covers blocking behavior, terminal states, timeout (default 180s, max 600s), and return object on timeout. Transparent and complete.

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?

Concise, well-structured, front-loaded with essential behavior. Every sentence adds value without verbosity.

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?

Completes the picture for a blocking wait tool: explains return behavior, timeout handling, integration with appcrane_deploy, and no output schema needed because description covers return format. All relevant context included.

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 covers both parameters with descriptions (100% coverage). Description adds context that deployment_id comes from appcrane_deploy but doesn't substantially enhance semantic meaning beyond the schema.

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 deployment reaches a terminal state and returns final status. It distinguishes from siblings like appcrane_get_logs (polling) and appcrane_deploy (triggering).

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 to use after appcrane_deploy instead of polling appcrane_get_logs, describes immediate return if terminal, and explains timeout behavior. Full guidance provided.

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