Collaborator: Reject Review

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

The description states 'rejects' indicating a mutation action, but annotations set readOnlyHint=true and destructiveHint=false, which is a contradiction. This misleads the agent about the tool's behavior.

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 concise and includes the parameter list, which is helpful. It is front-loaded with the main action. No unnecessary repetition.

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 the annotation contradiction, the description fails to clarify the true behavior. It does not explain the effect of rejection, whether it is reversible, or any permissions needed. No output schema exacerbates the lack of completeness.

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 100%, and the description merely lists the parameters without adding extra semantic value beyond what the schema provides.

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 clearly states the verb 'rejects' and resource 'review', and specifies that it uses review ID and reason. It distinguishes itself from sibling collaborator tools like create_review 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?

No guidance on when to use this tool versus alternatives, no mention of prerequisites or conditions under which rejection is appropriate.

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