openclaw_exec_approval_waitDecision

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

Discloses blocking nature, long-running duration, and timeout bounded by request timeout. No annotations provided, so description carries burden; it effectively conveys key behaviors. However, does not specify error handling (e.g., what happens on timeout or cancellation).

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 redundant information. Front-loaded with action and result. Each sentence earns its place.

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, no annotations, and description omits return value behavior (e.g., what does it return on timeout? error? null?). For a blocking wait, missing details on timeout handling and response structure makes it incomplete.

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 description coverage is 67% (id and instance described). Description adds no new meaning for id or instance beyond schema, and fails to describe timeoutMs parameter which lacks schema description. Baseline for high coverage is 3 but one param ignored, reducing score.

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?

Description clearly states the tool blocks until an exec approval gets a decision or times out, distinguishing it from siblings like openclaw_exec_approval_get (non-blocking) and openclaw_exec_approval_request (creates requests). Verb 'Block until' plus resource 'exec approval decision' is specific.

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?

Description implies use when waiting for a decision by stating it blocks, but does not explicitly contrast with alternatives like openclaw_exec_approval_get for non-blocking checks or mention when not to use. Lacks explicit when-not and alternative guidance.

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