github_list_pull_request_review_comments

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

With no annotations, the description bears full burden for behavioral disclosure. It mentions routing and authentication context (JWT, tenant, company scope), which is helpful, but omits whether the tool is read-only, has side effects, or what data it returns. Essential behavioral traits like idempotency or rate limits are absent.

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 short but contains redundancy (repeating the name in two ways). The routing details are useful but could be condensed. Overall, it is acceptably brief but not optimally concise.

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?

Despite having an output schema, the description does not explain what the tool returns (list of review comments). It lacks details on filtering, pagination, or how to structure arguments. The routing context is present but insufficient for a complete understanding of tool usage.

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 only parameter 'arguments' has no description in the schema (0% coverage). The description merely states it is a JSON string of arguments without specifying expected fields like owner, repo, pull_number, or pagination. This adds negligible meaning beyond the schema definition.

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 identifies the tool as listing pull request review comments from GitHub, clearly stating the operation and platform tool names. It distinguishes itself from sibling GitHub tools like github_list_pull_request_files or github_list_reviews by specifying 'review comments', though it does not explicitly state the scope (e.g., which pull request).

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 is no guidance on when to use this tool versus alternatives. No context is provided about scenarios that call for listing review comments, nor are there any exclusions or prerequisites mentioned. The description only describes the routing mechanism.

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