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 states the action but doesn't describe what 'request changes' entails behaviorally—does it block merging, send notifications, require specific permissions, or have side effects? The return statement mentions 'confirmation or error message' but gives no details on format or content. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 with a clear purpose statement followed by Args and Returns sections. It's concise at three sentences with no redundant information. However, the 'Args' and 'Returns' sections are under-specified rather than overly verbose, which is a content issue rather than a structural one.

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?

For a mutation tool with 3 parameters (0% schema coverage), no annotations, and an output schema (though not provided in detail), the description is incomplete. It lacks critical context: what 'request changes' does in Bitbucket's workflow, permission requirements, error conditions, and detailed parameter semantics. The presence of an output schema might cover return values, but the description doesn't compensate for the missing behavioral and parametric context.

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 schema provides no parameter documentation. The description lists parameters in an 'Args' section but only gives minimal labels (e.g., 'Repository slug (name)') without explaining what a 'slug' is, how to find the 'pr_id', or when 'workspace' is needed. It doesn't clarify if 'workspace' is the user's default or must match the repository's workspace, leaving key semantic gaps despite naming the parameters.

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 action ('Request changes') and target resource ('on a Pull Request on Bitbucket Cloud'), which is specific and unambiguous. It doesn't explicitly differentiate from siblings like 'decline_pull_request' or 'add_pull_request_comment', but the verb 'request changes' is distinct enough to imply a specific review action rather than general commenting or rejection.

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 like 'add_pull_request_comment', 'approve_pull_request', or 'decline_pull_request'. There's no mention of prerequisites (e.g., reviewer status), typical workflow context, or what constitutes 'requesting changes' versus other review actions. The agent must infer usage from the tool name alone.

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