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 states the action is to 'decline/close' (implying a destructive mutation), it doesn't mention permission requirements, whether the action is reversible, rate limits, or what specific confirmation message format to expect. For a destructive operation with zero annotation coverage, this is insufficient.

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 efficiently structured with a clear purpose statement followed by well-organized parameter explanations and return information. Every sentence adds value, though the 'Args:' and 'Returns:' formatting could be slightly more concise.

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 this is a destructive mutation tool with no annotations but with an output schema (implied by 'Returns: Confirmation or error message'), the description covers the basic purpose and parameters adequately. However, for a tool that permanently closes pull requests, more behavioral context about permissions, irreversibility, and error conditions would be beneficial.

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 provides meaningful semantic context for all 4 parameters: 'repo_slug' is explained as 'Repository slug (name)', 'pr_id' as 'Pull Request ID to decline', 'reason' as 'Optional reason for declining (will be added as a comment)', and 'workspace' as 'Bitbucket workspace (optional if configured)'. This compensates well for the schema's lack of descriptions.

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 ('Decline/close a Pull Request'), specifies the resource ('on Bitbucket Cloud'), and distinguishes it from alternatives by explicitly stating 'without merging'. This differentiates it from sibling tools like 'merge_pull_request' and 'update_pull_request'.

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 by stating this tool declines/close pull requests 'without merging', which implicitly suggests when to use it versus merging alternatives. However, it doesn't explicitly mention when NOT to use it or name specific alternative tools beyond the implied contrast with merging.

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