wait_for_review

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

No annotations provided, but description discloses blocking behavior, timeout, return verdict format, and re-call hint. Does not cover auth or error cases, but key behavioral traits are addressed.

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?

Three effective sentences with zero waste. Front-loaded with main action, return format, and pairing hint. Every 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?

Given well-described schema and no output schema, description adequately covers return format and pairing. Could mention blocking duration limit implicitly, but overall complete for the use case.

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 100% (baseline 3). Description adds value: explains review_id origin, channel default (SLACK_DEFAULT_CHANNEL), and the re-call hint on timeout. Enhances parameter understanding.

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 explicitly states the verb 'Block' and the resource 'human reaction/reply in review thread', distinguishing from siblings like check_review (non-blocking) and wait_for_reply (replies only).

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?

Clear context: blocks until human reacts/replies or timeout, and explicitly pairs with send_to_slack's review_id. Lacks explicit when-not-to-use or alternatives but is sufficient.

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