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 mentions pagination defaults and limits ('max 100'), which is useful, but lacks critical details: authentication requirements, rate limits, error handling (e.g., invalid PR IDs), or whether it's a read-only operation (implied by 'Get' but not explicit). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 organized sections for Args and Returns. Each sentence adds value: the first states the action, and the parameter explanations are necessary given low schema coverage. It avoids redundancy but could be slightly more concise by integrating pagination details into the main flow.

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 covers parameters well and hints at returns ('List of comments with details'), but lacks full behavioral context (e.g., auth, errors). The output schema likely defines the return structure, so the description doesn't need to detail it further, but overall completeness is moderate due to missing operational guidelines.

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 context for all 5 parameters: explains 'repo_slug' as 'Repository slug (name)', 'pr_id' as 'Pull Request ID', clarifies 'workspace' as optional with a default, and details pagination behavior ('page' and 'pagelen' with defaults and max). This goes beyond the bare schema, providing practical usage insights, though it could note format specifics (e.g., numeric PR IDs).

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 verb ('Get') and resource ('comments from a Pull Request on Bitbucket Cloud'), making the purpose unambiguous. It distinguishes from siblings like 'get_pull_request' (which retrieves PR metadata) and 'list_commit_comments' (which targets commits rather than PRs), though it doesn't explicitly name these alternatives. The specificity is good but lacks explicit sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid PR ID), contrast with similar tools like 'get_pull_request_activity' (which might include comments), or specify use cases (e.g., reviewing feedback). The description assumes the user knows when to fetch PR comments without offering context.

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