list_pull_reviews

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

The readOnlyHint annotation already covers the safety profile, and the description does not contradict it. No additional behavioral details like pagination, ordering, or response limitations are provided, but none are required for this simple read-only listing operation.

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, front-loaded sentence with no filler. It is concise and readable, though it could have used one more clause to clarify the 'index' parameter.

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?

The output schema and readOnlyHint annotation cover some context, but the description leaves parameter semantics under-specified and does not distinguish clearly enough from related pull request review tools. Adequate for a simple list, but with clear gaps.

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 schema has 0% description coverage, and the tool description does little to compensate. 'owner' and 'repo' are interpretable from naming conventions, but 'index' is left ambiguous and is only weakly tied to the pull request by the phrase 'on a pull request.'

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 (List), the resource (reviews), and the scope (on a pull request). It is specific enough to be distinguished from siblings like list_pull_review_comments and get_pull_review.

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 intended use is implied: use this when you need all reviews for a pull request. However, it does not explicitly mention when to prefer get_pull_review or list_pull_review_comments, so routing guidance is weak.

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