Collaborator: ReviewService Action

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

The description contradicts the annotations: readOnlyHint=true while the described generic invocation plus schema actions such as cancel, reopen, and uncancel imply state-changing behavior. It also fails to disclose side effects, preconditions, or failures for the supported action enum.

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 text is short and the core purpose is front-loaded, but it wastes space repeating parameter metadata from the schema and the Toolset line, and it front-loads an inaccurate sentence. The structure is neat but the content is not reliable.

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?

For a generic dispatcher with a nested free-form args object and no output schema, the description is severely incomplete: it omits valid action semantics, return values, error behavior, and examples. An agent cannot determine how to construct args for any of the four actual enum values.

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 0% and the description does not compensate for the actual enum actions. It only documents reviewId/until for finishReviewPhase and waitOnPhase, which are not valid action values, leaving args for moveReviewToAnnotatePhase, cancel, reopen, and uncancel completely unspecified.

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 says it can 'Invoke any ReviewService method by name and arguments,' which identifies a generic dispatch tool on a specific service, but 'any method' is contradicted by the action enum and by mentioning finishReviewPhase/waitOnPhase that are not in that enum. It does not distinguish this generic action from the dedicated collaborator_* review tools.

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 explicit when-to-use or alternative selection guidance is provided. The only usage detail is for two methods absent from the schema enum, and there is no indication that dedicated tools should be preferred for common operations such as creating or rejecting a review.

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