Collaborator: Reject Review

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

The description states 'Rejects a review,' which implies a state-changing action, but the annotations declare readOnlyHint=true and idempotentHint=true. Rejecting a review is not read-only, so the description directly contradicts the annotation metadata. No additional behavioral context such as side effects, permissions, or irreversibility is provided.

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 core description is one concise, front-loaded sentence that clearly states the action and key inputs. The subsequent parameter block and toolset line add some redundancy with the schema but do not make the description bloated or hard to parse.

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?

This is a mutation-like operation with no output schema and no explanation of the result or side effects of rejecting a review. The annotation contradiction makes the behavioral model unreliable, leaving an agent unsure whether the tool modifies state. A simple 2-parameter schema does not compensate for the missing usage and behavioral context.

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%, and the description's parameter list simply duplicates the schema's field names and descriptions. It adds no new semantic detail such as value formats, constraints, or relationships between reviewId and reason. The baseline of 3 is appropriate because the schema already documents both parameters.

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 opens with a specific verb and resource: 'Rejects a review in Collaborator'. It also names the required inputs, 'by its review ID and reason', making the operation unambiguous. Among many sibling tools, this is clearly the reject-review operation rather than create, find, or get reviews.

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 gives no guidance on when to use this tool versus alternatives such as collaborator_reviewservice_action, collaborator_get_reviews, or collaborator_find_review_by_id. The 'Toolset: Review Management' line only categorizes the tool; it does not explain conditions for use or exclusions.

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