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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable detail about the response content (status, user response status, awaited participants, etc.) beyond those flags. It does not contradict annotations and gives a fuller picture of what a successful call returns.

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 a single, fairly dense sentence that front-loads the core action ('Lists reviews...') and packs in the relevant details. It is efficient, though slightly long; still, every clause adds information, earning a 4.

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 that the tool has an output schema (indicated by context signals), the description sufficiently covers the purpose and returned scope without needing to spell out return values. It does not address pagination or sorting, but those are likely handled by the output schema or are minor for a listing tool. Overall complete for an agent to invoke it correctly.

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?

The sole parameter 'status' is fully described in the schema (enum open/closed). The description does not add any additional meaning or constraints beyond the schema. With 100% schema coverage, the baseline of 3 is appropriate.

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?

Clearly states it lists reviews for a user (participant or creator) and enumerates the included details (status, response status, awaited participants, title/reference, and invention for report reviews). It implicitly distinguishes from the single-review sibling get_review by using the plural 'list' and listing multiple returned attributes.

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?

Provides context that the user must be a participant or creator, but does not explicitly mention when to use this vs. alternatives like get_review, nor does it note exclusions (e.g., not for admin viewing all reviews). The usage is implied but not explicit.

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