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 details but does not describe authentication requirements, rate limits, error conditions, or whether it's a read-only operation (implied by 'Get' but not explicit). The mention of returned information is basic and lacks depth on format or completeness.

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 and return details. It uses bullet-like sections ('Args:', 'Returns:') for clarity. However, the 'Returns' section could be more concise by integrating with the purpose statement, and some redundancy exists (e.g., repeating 'Pull Request').

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 moderate complexity (3 parameters, no annotations, but with an output schema), the description is adequate but has gaps. It covers purpose and parameters but lacks usage guidelines, behavioral details, and error handling. The output schema existence reduces the need to detail return values, but the description should still address when and how to use the tool effectively.

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 semantics: 'repo_slug' is clarified as 'Repository slug (name)', 'pr_id' as 'Pull Request ID', and 'workspace' as 'Bitbucket workspace (optional if configured)'. This provides essential context beyond the bare schema types, though it could elaborate on format expectations (e.g., slug conventions).

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: 'Get details of a specific Pull Request on Bitbucket Cloud.' It specifies the verb ('Get details'), resource ('Pull Request'), and platform ('Bitbucket Cloud'), making the intent unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_pull_request_activity' or 'get_pull_request_comments', which target specific aspects of pull requests rather than general details.

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 sibling tools like 'list_pull_requests' for listing PRs or 'get_pull_request_activity' for activity logs, nor does it specify prerequisites such as authentication or workspace configuration. The optional 'workspace' parameter hint is minimal and lacks context.

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