Get pull request threads

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. It only states that the tool lists top-level and inline threads; it does not mention pagination behavior, iteration filtering, response shape, or any side effects. This is minimal and leaves important behavior unknown.

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, front-loaded sentence that earns its place. It has no filler, repetition, or irrelevant detail, making it easy for an agent to parse quickly.

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?

The tool has 7 parameters, no output schema, and many related siblings, yet the description only gives the basic listing scope. Missing context includes pagination handling, iteration semantics, and how this differs from thread-comment retrieval. An agent would likely need to inspect the schema or guess to invoke it correctly in non-trivial cases.

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 43%, and the description adds no explanation of the undocumented parameters like top, iteration, baseIteration, or continuationToken. It also does not clarify how the 'top-level and inline' scope maps to those parameters, so it does not compensate for the low 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 uses a specific verb ('List') and identifies the resource ('comment threads on a pull request'), plus clarifies the scope ('top-level and inline'). It is clear on its own, though it does not explicitly distinguish itself from the closely named sibling get_pull_request_thread_comments.

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?

No guidance is provided about when to use this tool versus alternatives such as get_pull_request_thread_comments, create_pull_request_comment, or update_pull_request_thread_status. There are no exclusions, prerequisites, or context signals to steer an agent toward the correct sibling.

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