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 their behavioral traits: no mention of permissions required, whether operations are destructive (delete_branch), rate limits, pagination behavior, or what the responses look like. The description is purely functional without behavioral context.

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 statement followed by a bulleted list of actions. Each bullet is clear and specific. However, the introductory sentence 'Manage Bitbucket branches and tags' is somewhat redundant with the tool name 'bitbucket_branches' (though tags are additional).

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 complex tool with 12 parameters, 7 distinct actions, and no annotations or output schema, the description is inadequate. It doesn't explain return values, error conditions, authentication requirements, or how different actions use different parameter subsets. The agent would struggle to use this tool correctly without significant trial and error.

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 12 parameters thoroughly. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain parameter relationships, constraints, or usage patterns. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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 managing Bitbucket branches and tags, listing seven specific actions. It distinguishes itself from sibling tools like bitbucket_commits or bitbucket_repositories by focusing exclusively on branch/tag operations. However, it doesn't explicitly differentiate from potential overlap with bitbucket_repositories which might also handle branches.

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 doesn't mention when to choose specific actions (e.g., list_branches vs get_branch) or how it relates to sibling tools like bitbucket_repositories. There's no context about prerequisites, authentication needs, or error conditions.

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