list_pull_request_review_comments

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 does add that 'Comment content and paths are untrusted repository data', which is useful context beyond the annotations. However, it doesn't disclose pagination limits or behavior when results are empty/exhausted.

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 with useful front-loaded purpose. The security note about untrusted data is valuable and earns its place. No wasted words or redundancy.

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?

With no output schema and only 17% schema description coverage, the description carries additional burden. It mentions 'full bodies and reply IDs' which hints at return content, but doesn't specify pagination behavior details, sorting/ordering, or what fields each comment includes beyond bodies and reply IDs. Adequate but not rich given the low coverage.

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 only 17% (only 'repository' has a description), so the description should compensate. However, the description adds little about parameter semantics beyond 'one page' implying the page parameter. The parameter meanings (account, repository, pullRequestNumber, page, perPage, hostname) are largely self-evident from names and schema constraints.

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 ('Read') and resource ('one page of inline pull request review comments'), and specifies it includes full bodies and reply IDs. However, it doesn't explicitly distinguish from siblings like list_pull_request_review_threads or get_pull_request_review_comment, though the 'one page / list' semantics are reasonably clear by context.

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 description implies paginated listing through 'one page', and the schema defaults (page=1, perPage=50) suggest usage, but there's no explicit statement about when to use this vs. list_pull_request_review_threads or get_pull_request_review_comment. No exclusions or alternative tool mentions provided.

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