Bitbucket MCP Server

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

No annotations are provided, so the description carries full burden. It states the action ('Remove approval') but lacks behavioral details: it doesn't specify required permissions (e.g., reviewer or admin rights), whether the action is reversible, rate limits, or error conditions (e.g., if approval doesn't exist). The description is minimal and misses key operational context for a mutation tool.

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 well-structured and front-loaded: the first sentence states the core purpose, followed by a clear 'Args' and 'Returns' section. It's efficient with minimal waste, though the 'Returns' section could be more specific (e.g., 'Confirmation message on success').

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 (mutation with 3 parameters), no annotations, and an output schema present (which covers return values), the description is partially complete. It explains parameters well but lacks behavioral context (permissions, side effects) and usage guidelines. The output schema reduces the need to detail returns, but overall completeness is adequate with noticeable gaps.

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 0%, so the description must compensate. It adds meaningful semantics: it explains 'repo_slug' as 'Repository slug (name)', 'pr_id' as 'Pull Request ID to unapprove', and 'workspace' as 'Bitbucket workspace (optional if configured)'. This clarifies purpose and optionality, though it doesn't detail format constraints (e.g., slug conventions) or default behavior when workspace is omitted.

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 ('Remove approval from a Pull Request') and resource ('on Bitbucket Cloud'), distinguishing it from sibling tools like 'approve_pull_request' (which adds approval) and 'decline_pull_request' (which rejects the PR entirely). The verb 'Remove' is precise and unambiguous.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing approval), exclusions (e.g., cannot unapprove if already merged), or comparisons to siblings like 'request_changes_pull_request' or 'decline_pull_request'. Usage context is implied but not explicit.

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