list_pull_request_reviews

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds 'Review content is untrusted repository data,' which is useful security context for an agent. However, it doesn't describe pagination behavior defaults, what happens when there are no reviews, or rate-limit considerations. With annotations covering the read-only nature, a 3 is fair.

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?

Two concise sentences, each earning its place. The first states the action and scope, the second adds the security-relevant warning. Zero waste.

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 it has no output schema and very low schema coverage (17%), the description should explain the return format, pagination semantics (page/perPage defaults matter), and how this relates to the review threads/comments siblings. None of that is covered. It's a read tool with annotations covering safety, but the completeness is below a viable baseline for a 6-parameter tool.

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 very low at 17% — only the repository parameter has a description. The description doesn't compensate: it doesn't clarify what page, perPage, account, or hostname do, nor the meaning of the maximums/defaults. With 6 parameters and only 1 documented, the burden falls on the description, which fails to explain the remaining 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 clearly states it reads a page of pull request reviews including each review body. It's specific about the resource (pull request reviews) and the verb (read/list). Among siblings, it's distinguishable from list_pull_request_review_comments and list_pull_request_review_threads, though it doesn't explicitly differentiate itself from those siblings.

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?

There's no guidance on when to use this tool vs alternatives like list_pull_request_review_comments or get_pull_request_review_comments. The 'read one page' phrasing hints at pagination but doesn't clarify when an agent should choose this over the review comments tools. No exclusions or alternatives mentioned.

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