Collaborator: Create Review

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

The description claims 'Creates a new review', a write operation, but annotations declare readOnlyHint=true, a serious contradiction. Also no disclosure of side effects or requirements.

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?

Concise: one line summary plus parameter list. No extraneous text. However, the list could be more compact.

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. Description lacks info about the created review object or error handling. All parameters are optional, so baseline completeness, but missing return 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 coverage is 100%, so baseline 3. The description repeats parameter defaults (e.g., creator defaults to logged in user) but adds little beyond the schema. No enum values or advanced semantics.

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 'Creates a new review in Collaborator', which is a specific verb+resource. It distinguishes itself from sibling tools like collaborator_find_review_by_id and collaborator_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 (e.g., collaborator_get_reviews for viewing reviews). The description only states what it does, not when to choose it.

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