Bitbucket MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves configuration details, implying a read-only operation, but does not specify error conditions (e.g., if the repository doesn't exist), authentication requirements, rate limits, or whether the data is cached. This leaves significant gaps in understanding how the tool behaves in practice.

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 with the core purpose, followed by clear sections for arguments and returns. Every sentence adds value, with no redundant information. It could be slightly more concise by integrating the optional note into the parameter list, but overall it is efficient and easy to parse.

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 low complexity (simple retrieval), 2 parameters with semantic clarification in the description, and the presence of an output schema (which handles return details), the description is largely complete. It covers the what, parameters, and returns adequately, though it lacks behavioral context like error handling or prerequisites, which holds it back from a perfect score.

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?

The description adds meaningful context for both parameters: 'repo_slug' is clarified as the repository name, and 'workspace' is noted as optional if configured, which helps understand when it can be omitted. With 0% schema description coverage, this compensates well, though it could detail format constraints (e.g., slug format) or default behaviors more explicitly.

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 tool's purpose with a specific verb ('Get') and resource ('branching model configuration for a repository'), distinguishing it from sibling tools that focus on operations like creating branches, pull requests, or repositories. It precisely identifies what is being retrieved without ambiguity.

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 does not mention prerequisites, such as whether the repository must exist or have a configured branching model, nor does it differentiate from other configuration-related tools like 'get_config_status' or 'get_repository'. Usage context is implied but not explicitly stated.

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