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. It states the action ('Add a comment') but doesn't mention permissions required, rate limits, whether the comment is editable/deletable, or how it interacts with pull request workflows. The mention of markdown support is a useful detail, but overall, critical behavioral context is missing 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 with the core purpose, followed by parameter explanations and return info. It uses bullet-like formatting for clarity. While efficient, the 'Returns' section could be more specific, but overall, it's concise with minimal waste.

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 no annotations, 0% schema coverage, and an output schema present, the description does an adequate job. It explains parameters and hints at returns, but as a mutation tool, it lacks details on permissions, side effects, or error handling. The output schema reduces the need to describe return values, but behavioral gaps remain.

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 meaning by explaining each parameter's purpose (e.g., 'Repository slug (name)', 'Comment text (supports markdown)') and notes workspace is optional if configured. However, it doesn't clarify formats (e.g., what a 'slug' is) or constraints, leaving gaps despite covering all 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 ('Add a comment') and target resource ('to a Pull Request on Bitbucket Cloud'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'add_inline_comment' and 'add_issue_comment' by specifying it's for pull requests. However, it doesn't explicitly contrast with these similar tools, keeping it from a perfect score.

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_inline_comment' or 'reply_to_comment'. It mentions the workspace parameter is optional 'if configured', which hints at a prerequisite but doesn't explain configuration or usage contexts. There's no explicit when/when-not advice or comparison to sibling tools.

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