bb_get_pr_all_file_diffs

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

The annotations already declare readOnlyHint=true, so the read-only nature is covered by structured metadata. The description adds useful behavioral context beyond the name by emphasizing the single-call aggregation and efficiency advantage over per-file calls. No contradictions with annotations are present.

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, efficient sentence that communicates both the tool's function and its key benefit. It is front-loaded with the core purpose and contains no redundant or filler wording.

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 read-only tool with a clear output schema and thoroughly documented parameters, the description is sufficient to guide correct invocation. It could additionally mention cases where per-file diff retrieval might be preferable, but overall the context provided is strong.

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?

The input schema has 100% description coverage, with each parameter including a clear explanation and relevant defaults. The description adds no additional parameter-level detail, so the schema carries the semantic burden as expected; a baseline score of 3 is 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?

The description clearly identifies the action ('Get'), the resource ('the complete diff for every modified file in a pull request'), and the batching benefit over the sibling tool bb_get_pr_file_diff. This makes the tool's purpose unambiguous and easily distinguishable from similar siblings.

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 description explicitly names bb_get_pr_file_diff as the per-file alternative and states that this tool is 'much more efficient' for multi-file diffs. It gives the agent a clear reason to choose this tool for whole-PR diff retrieval, though it stops short of explicitly saying when to prefer the single-file variant.

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