oc_task_wait

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

Adds 'block' behavior beyond annotations (readOnlyHint=true, idempotentHint=true). Describes timeout behavior. No contradictions; annotations are consistent with a read-only wait operation.

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?

Single clear sentence, front-loaded with purpose and states default. No wasted words.

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?

Covers core behavior and timeout. No output schema, so return value is implicit. Annotations provide safety context. Could mention return value, but adequate for a simple blocking tool.

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 has 50% description coverage; task_id is described, timeout_ms is not. Description adds default timeout value but not min/max constraints or usage tips. Provides some added value but incomplete.

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 blocks until a task reaches terminal state or timeout. Verb 'block' and resource 'task' are specific. Distinguishes from siblings like oc_task_get (non-blocking status check).

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?

Implies use when waiting for task completion. Mentions default timeout. No explicit exclusions or alternatives, but sibling tools (e.g., oc_task_get) exist for non-blocking checks.

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