get_pull_request_comments

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

With no annotations, the description carries the full burden of behavioral disclosure but only restates the tool's name. It does not mention pagination semantics, authentication needs, return format, or the fact that 'all comments' may require multiple page requests. The schema hints at pagination, but the description itself is silent.

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 six-word sentence that is extremely concise and front-loaded. Every word contributes to the meaning, with no redundancy or irrelevant 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?

While the tool is simple and the schema is informative, the lack of an output schema and annotations leaves gaps. The description does not clarify the return shape or the need for pagination to truly retrieve 'all' comments, making it only minimally complete for the agent.

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?

Since the schema provides 100% coverage with descriptions for all four parameters, the description adds no additional semantic value beyond what is already in the schema. The baseline score of 3 is appropriate.

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 states the action ('Get') and the specific resource ('all comments from a pull request'), clearly distinguishing it from sibling tools like get_pull_request and add_pull_request_comment. It is specific and unambiguous.

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 provides no explicit when-to-use guidance, exclusions, or mention of alternative tools. Usage is only implied by the verb 'Get' and the resource name, which is insufficient for decision-making in ambiguous contexts.

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