Get pull request review context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly describes the output contents, which is useful, but it does not disclose behavior around optional parameters, truncation limits (e.g., maxFiles, diffMaxLines), authentication requirements, or whether any defaults suppress parts of the bundle.

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, well-structured sentence that front-loads the action and result, then lists the contents of the bundle without filler. Every part adds information.

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 9 parameters, no output schema, no annotations, and a large sibling set, this one-sentence overview is not complete. It fails to clarify how include flags affect the response, what maxFiles/diffMaxLines limit, or how this tool relates to the individual get_pull_request_* siblings. An agent would need additional reasoning to invoke it correctly with confidence.

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 33%, and the description does not compensate sufficiently. It mentions the output components that map to includeCommits, includeThreads, includeReviewers, and includeWorkItems, but it does not explain how those flags control the bundle or what maxFiles and diffMaxLines do. An agent cannot infer parameter behavior from this text.

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 names a specific verb ('Return'), a distinct resource ('PR review context'), and enumerates exactly what the bundle contains: metadata, diff summary, unified diff, commits, threads, reviewers, and work items. This clearly differentiates it from the many granular sibling tools like get_pull_request_diff and 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 'in one review bundle' implies this is a convenience aggregation tool meant for fetching everything in a single call rather than using separate sibling calls. However, it does not explicitly state when to choose this over the granular alternatives, nor does it mention any exclusions or prerequisites.

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