Collaborator: ReviewService Action

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

Annotations indicate readOnlyHint=true and destructiveHint=false, but the included actions (cancel, reopen, uncancel) are clearly mutative. This contradiction undermines transparency. The description also fails to disclose behavioral traits for the listed actions.

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 short but includes irrelevant details (actions not in schema) and omits critical information. It is not efficiently structured for agent comprehension.

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, incomplete parameter descriptions, and contradictory annotations leave significant gaps. Agents cannot reliably infer return values or side effects.

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%. The description gives parameter hints for finishReviewPhase and waitOnPhase (not in the schema), but for the actual enum actions, no parameter details are provided. The args parameter is an opaque record, leaving agents uninformed.

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 states 'Invoke any ReviewService method' but the schema enum only lists four actions (moveReviewToAnnotatePhase, cancel, reopen, uncancel). It also mentions 'finishReviewPhase' and 'waitOnPhase' which are not in the enum, causing confusion. The purpose is somewhat clear but misleading due to mismatches.

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?

No guidance on when to use this tool versus sibling tools like collaborator_create_review or collaborator_reject_review. It does not specify scenarios where invoking these generic actions is appropriate.

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