Bitbucket MCP

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 lists actions but doesn't describe side effects, permissions required, rate limits, error conditions, or response formats. For example, it doesn't clarify if 'merge' is irreversible, what 'approve' entails, or how pagination works with 'list' actions. This leaves significant gaps for a tool with 22 parameters and multiple mutation actions.

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 efficiently structured with a brief introductory phrase followed by a bulleted list of actions. Each bullet is clear and specific. However, the list format could be more front-loaded with critical guidance, and some bullets (like 'list' and 'get') are very brief without additional context.

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 complexity (22 parameters, 11 actions including mutations), no annotations, and no output schema, the description is insufficient. It doesn't explain return values, error handling, authentication requirements, or important behavioral details like whether actions are idempotent or have side effects. For a multi-action tool with significant functionality, this leaves too many unknowns.

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 100%, so the schema already documents all 22 parameters thoroughly. The description adds minimal value beyond the schema by listing action names that correspond to the 'action' enum, but doesn't provide additional context about parameter relationships or usage. This meets the baseline for high schema coverage.

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 as 'Manage Bitbucket pull requests' and enumerates 11 specific actions, providing a comprehensive overview of what the tool does. It distinguishes itself from siblings like bitbucket_branches or bitbucket_issues by focusing exclusively on pull request operations. However, it doesn't explicitly contrast with these siblings beyond the domain difference.

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 lists actions but doesn't indicate prerequisites, when certain actions are appropriate (e.g., merge vs. decline), or how it relates to sibling tools like bitbucket_commits or bitbucket_repositories. The agent must infer usage from the action list alone.

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