Atlassian 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 and does well by disclosing key behavioral traits: it describes the output format ('formatted Markdown showing file changes, additions, and deletions'), authentication requirements ('Requires Bitbucket credentials'), and operational constraints ('Limits the number of files to show'). However, it doesn't mention rate limits, error conditions, or whether the operation is read-only.

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 appropriately sized with three sentences that each earn their place: first states the core operation, second adds parameter context, third covers output format and authentication. It's front-loaded with the main purpose, though the second sentence could be slightly more concise.

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 7 parameters, no annotations, and no output schema, the description provides good coverage of what the tool does, its output format, and authentication needs. It could be more complete by explicitly stating this is a read-only operation and mentioning any limitations on branch naming or repository access.

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 7 parameters thoroughly. The description adds minimal value beyond the schema, mentioning only the purpose of the limit parameter and the workspaceSlug/repoSlug identification context. Baseline 3 is appropriate when the schema does the heavy lifting.

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 with specific verbs ('shows changes', 'compares changes') and resources ('branches in a repository'), distinguishing it from siblings like bb_diff_commits (which compares commits) and bb_list_branches (which lists branches). It specifies the exact comparison operation between source and destination 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 implies usage context by stating it compares branches in a repository, but doesn't explicitly say when to use this tool versus alternatives like bb_diff_commits or bb_get_commit_history. It mentions Bitbucket credentials requirement, which is a prerequisite but not a usage guideline relative to other tools.

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