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. It only states 'Get comment threads on a pull request.' No disclosure of pagination, thread resolution status, read-only nature, or authentication requirements. Minimal insight beyond the name.

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 very short (one sentence plus args list). No extraneous words, but the arguments section is awkwardly placed in the description. Could be integrated more naturally.

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?

Given no annotations and 3 parameters with no required ones, the description should explain default behavior (e.g., what default project means), ordering of threads, or pagination. The output schema exists but the description omits important context, leaving gaps.

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 coverage is 0%, so description must compensate. It adds basic clarifications: project 'uses default if not specified', repository_id is 'ID or name', pull_request_id is 'the pull request ID'. These are minimal but better than nothing, earning a baseline 3.

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 'Get comment threads on a pull request.' This is a specific verb-resource combination ('get' + 'comment threads') and distinguishes from siblings like 'get_pull_request' (PR details) and 'create_pull_request_comment' (create operation).

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 on when to use this tool versus alternatives (e.g., 'get_work_item_comments' for work items). No mention of prerequisites or typical usage scenarios.

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