list_pull_review_comments

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

The readOnlyHint annotation already declares the operation is read-only, so the description primarily adds scoping context. It does not mention pagination, ordering, or that this returns review comments rather than general PR comments, but it does not contradict the annotation.

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 zero wasted words. It states the action and the target resource immediately, making it easy for an agent to process quickly.

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 relieve some burden, and the action is simple, but the description leaves the 'index' parameter undefined and does not hint at the prerequisite workflow of obtaining a review_id. It is adequate for a straightforward list operation but incomplete for reliable invocation.

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 0%, so the description carries the burden of explaining parameters. It fails to clarify the ambiguous 'index' parameter, which is likely the pull request number, and does not explain how 'review_id' maps to the review. Owner and repo are obvious, but the description adds no semantic value beyond the parameter names.

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 uses a specific verb ('List') and names the exact resource ('comments on a specific pull request review'). This clearly differentiates it from sibling tools like list_pull_reviews, which list reviews, and list_issue_comments, which target issue comments.

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 phrase 'specific pull request review' implies the tool should be used when a review_id is already known, but the description does not explicitly state when to use this tool versus alternatives such as list_pull_reviews or get_pull_review. The usage is inferable but not explicitly guided.

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