get_pull_request_comments

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

No annotations are supplied, so the description carries the full disclosure burden and discloses almost nothing: it does not confirm this is a read-only operation, does not mention pagination behavior for 'top', and does not say whether deleted comments are excluded by default. For a 7-parameter retrieval tool this leaves meaningful behavioral questions unanswered.

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?

A single clear, front-loaded sentence with no wasted wording. Its brevity is efficient, though it edges toward under-specification given the tool's seven parameters.

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 annotations, no output schema, and seven parameters, the description should explain the return shape (threads vs. flat comments) and default filtering behavior. It supplies none of that, leaving the agent dependent entirely on the schema.

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 100%, so every parameter including top, threadId, includeDeleted, and organizationId is already documented in the schema. The description adds no meaning beyond that, making the baseline 3 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?

States a specific verb and resource ('get comments' from 'a specific pull request'), which is enough to distinguish it from write siblings like add_pull_request_comment or update_pull_request_thread_status. It does not, however, clarify how it differs from get_work_item_comments or whether thread-level versus PR-level retrieval is the point.

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 such as get_pull_request or get_pull_request_changes, and no mention of when the optional threadId/top/includeDeleted filters should be applied. The agent must infer all invocation context from the schema.

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