wait_dispatch

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

Discloses that the job is shielded from cancellation and that work continues if MCP call is aborted. No annotations provided, so description carries burden. Explains why default 50s is chosen.

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 concise paragraphs with no filler. Front-loaded with main purpose, each sentence adds value.

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 description implies response contains status field. Covers polling pattern and error recovery. Could mention return format or error codes.

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 0%; description adds meaning for max_wait_seconds by explaining its default and rationale. job_id is not explained further, remaining vague.

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 'Long-poll a job' and specifies the parameter max_wait_seconds. Distinguishes from siblings like get_dispatch (simple fetch) and cancel_dispatch (cancels).

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?

Provides explicit instructions to call in a loop and break on status != 'running'. Mentions re-entering with same job_id if aborted. Could be more explicit about when to use alternatives like get_dispatch.

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