Bitbucket MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the tool returns 'diff content as text', it doesn't describe important behavioral aspects like whether this is a read-only operation (implied but not stated), rate limits, authentication requirements, error conditions, or pagination for large diffs. The description provides basic output format but misses key operational context.

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 perfectly structured and front-loaded: purpose statement first, then organized parameter explanations, then return value. Every sentence earns its place - the opening statement defines the tool, the Args section documents parameters efficiently, and the Returns section clarifies output. No wasted words or redundancy.

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 the tool's moderate complexity (5 parameters, 2 required), 0% schema coverage, and presence of an output schema, the description does well but has gaps. The parameter documentation is excellent, and the output schema handles return values, but behavioral aspects (permissions, rate limits, error handling) are missing. For a read operation with no annotations, this is mostly complete but could benefit from safety/constraint information.

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?

With 0% schema description coverage, the description fully compensates by explaining all 5 parameters in the 'Args' section. Each parameter gets clear semantic explanation: repo_slug as 'Repository slug (name)', pr_id as 'Pull Request ID', file_path with usage guidance, context_lines with default value, and workspace with configuration note. This adds substantial value beyond the bare schema.

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 the specific action ('Get the diff') and resource ('for a Pull Request'), distinguishing it from sibling tools like get_pull_request (which retrieves metadata) and get_commit_diff (which operates on commits rather than PRs). The phrase 'code changes' in parentheses provides additional clarity about what a diff contains.

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 provides clear context for when to use optional parameters ('recommended for large PRs'), but doesn't explicitly state when to use this tool versus alternatives like get_pull_request_diffstat (which shows summary statistics) or get_commit_diff (for commit-level diffs). It offers practical guidance but lacks explicit sibling differentiation.

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