Dispatch to a Clanker and block until the turn completes

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

Beyond annotations (destructiveHint: true, etc.), the description adds that this tool blocks until the turn is terminal, and warns about potential MCP request timeouts for long tasks. It also specifies the return structure (WaitResult with fields status, final_message, etc.), which is not covered by annotations.

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?

The description is two sentences: the first explains the purpose and behavior, the second provides a usage guideline. It is concise, front-loaded, and contains 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?

Given the tool's complexity (blocking, 7 parameters, no output schema), the description explains the return structure and timeout concerns. It references sibling tools for long tasks. Missing error handling details, but overall adequate for a convenience wrapper.

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% with descriptions for all parameters, so baseline is 3. The description does not add additional parameter-level detail beyond the schema, but it provides context on the return structure (WaitResult) which compensates slightly for the lack of output 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 title and description clearly state the tool dispatches a Clanker and blocks until completion. It explicitly distinguishes itself from sibling tools like clanker_dispatch_start (which does not block) by describing it as a convenience path combining start and wait.

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 explicitly advises 'For long tasks prefer clanker_dispatch_start + clanker_wait' to avoid MCP request timeouts, providing clear when-to-use and when-not-to-use guidance with alternative tools.

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