Get batch pull request review summary

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

With no annotations, the description carries the safety/behavior burden. 'Summarize' and the tool name indicate a read-only aggregation, and the 50-PR cap is stated too. However, it does not disclose output shape, grouping, or whether unresolved threads include comments, leaving some behavior unexplained.

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?

One sentence, front-loaded, with no filler. Every phrase contributes: summarizes, votes/unresolved threads, batch limit.

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 four-parameter tool with no output schema and zero schema parameter descriptions, this definition is too thin. It omits how parameters select PRs, what 'summary' contains structurally, and when to prefer it over single-PR alternatives, leaving an agent to guess invocation semantics.

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 0%, so the description must compensate, but it never maps top, status, project, or repositoryId to how the batch is formed. Parameter names and the status enum provide limited self-evident meaning, but the important relationship between project/repositoryId/top and the summary is undocumented.

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 ('Summarize') and names the exact outputs (votes and unresolved threads), with a clear scope ('across up to 50 pull requests'). This distinguishes it as a batch aggregation tool from single-PR siblings like get_pull_request_reviewers or get_pull_request_threads.

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 phrase 'across up to 50 pull requests' implies a batch use case combined with filter parameters, but the description does not explicitly say when to choose this over single-PR review tools or what selection criteria apply. Usage context is present but only by implication.

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