Bitbucket MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively communicates the critical behavioral trait: 'This action is irreversible,' which is essential for a destructive operation. However, it doesn't mention authentication requirements, rate limits, or what happens to associated data (branches, issues, etc.).

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 appropriately sized, with a clear purpose statement upfront, followed by parameter and return value sections. Every sentence adds value, though the 'Returns' section could be slightly more informative given the output schema exists.

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 tool with no annotations, 2 parameters (0% schema coverage), and an output schema, the description does a good job covering essentials: purpose, irreversibility, and parameter meanings. However, it lacks details on error conditions, permissions, or side effects, which would enhance completeness for such a high-stakes operation.

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 provides basic semantic context for both parameters ('repo_slug: Repository slug (name)' and 'workspace: Bitbucket workspace (optional if configured)'), explaining what they represent. However, it doesn't clarify format details (e.g., slug syntax) or the 'optional if configured' condition, leaving some gaps.

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 ('Delete') and resource ('a repository'), distinguishing it from sibling tools like 'create_repository' or 'fork_repository'. It provides a precise verb+resource combination that leaves no ambiguity about the tool's function.

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 implies usage context through the warning 'This action is irreversible,' suggesting it should be used cautiously. However, it doesn't explicitly state when to use this tool versus alternatives (like 'delete_branch' or 'delete_snippet') or provide clear prerequisites or exclusions.

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