github_get_pr_comments

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

The description usefully discloses that both issue comments and review comments are included, which adds context beyond the tool name. However, with no annotations, it does not mention pagination, authentication prerequisites, or error behavior. The description carries the full burden but only partially covers behavioral traits.

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, well-structured sentence that front-loads the action and scope. Every word adds value, and there is no filler or unnecessary detail.

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?

For a simple three-parameter getter, the description adequately states what the tool does, but it lacks details about the return format, pagination, and authentication. Since there is no output schema and no annotations, this leaves some gaps for an agent deciding how to invoke and interpret the 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?

The input schema already covers all three parameters with generic descriptions (e.g., 'Repository name'). The tool description adds no extra parameter-specific context, so it earns the baseline score of 3 for high schema coverage.

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 'Get', the resource 'comments', and the scope 'for a specific pull request', distinguishing it from sibling tools like github_get_pr_details or github_get_pr_checks. Explicitly mentions both issue comments and review comments, leaving no ambiguity about what is returned.

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 makes it clear when to use this tool: when you need all comments for a pull request. It does not explicitly list alternatives or exclusions, but the context is obvious given the sibling tools. No conflicting guidance exists, so it earns a 4 for clear context without exclusions.

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