review_task

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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose meaningful state transitions: approve sends to completed and unblocks dependents, reject sends to revision_requested. However, it omits the behavior of the schema's 'request_changes' action, feedback requirements, and any idempotency or reversibility notes.

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 three concise sentences with no filler. The key action and status precondition are front-loaded, and every sentence contributes either scope, usage context, or state-transition behavior.

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 no annotations and no output schema, the description covers the main invocation context and critical state outcomes. It is not fully complete: the 'request_changes' action is omitted, feedback requirements are not mentioned, and the response/return behavior is not described. Overall, it is adequate but has clear gaps.

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 100%, so the baseline is 3. The description adds value beyond the schema by explaining that approve unblocks dependents and reject moves the task to revision_requested, enriching the action enum semantics. Feedback and reviewer parameters remain schema-only, but this is acceptable given full schema coverage.

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 uses a specific verb and resource: 'Approve or reject a task in needs_review status.' It also adds the human-gating context, which distinguishes this tool from sibling automation-oriented tools like complete_task. The core purpose is unambiguous, even though the schema's third action 'request_changes' is not named in the description.

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 clearly states the precondition ('task in needs_review status') and the intended usage context ('Used by humans to gate high-risk work'). It does not explicitly name alternatives or state when not to use this tool, so it stops short of full usage guidance.

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