bitbucket_pull_request_diff

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds that this returns a full unified diff and implicitly signals a heavier payload via 'only when file contents are actually needed,' which is useful cost context. It does not contradict the annotations.

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?

Two sentences with zero waste; the core purpose is front-loaded and the routing guidance follows naturally. Every clause earns its place.

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 fetch tool with no output schema, the description covers what is returned (full unified diff, optional file scoping) and when to use it. Combined with the rich schema and safety annotations, nothing essential an agent needs to invoke it correctly is missing.

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 75%, with path, repoSlug, and workspace already described in the schema. The description reinforces the path intent ('optionally scoped to one file') but adds no new parameter detail. The 'id' parameter remains undocumented in both schema and description, but it is self-evident. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States a specific verb and resource ('Get the full unified diff for a pull request') plus an optional scoping mode ('scoped to one file'). It explicitly differentiates from the sibling by declaring the diffstat distinction, so an agent can tell this apart from bitbucket_pull_request_diffstat without opening either schema.

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?

Provides explicit routing guidance: 'Prefer diffstat first; use this only when file contents are actually needed.' This names the alternative tool and the exact condition that should trigger selection, leaving nothing to inference.

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