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 specifies the output format ('formatted Markdown showing file changes, additions, and deletions'), authentication requirements ('Requires Bitbucket credentials to be configured'), and the comparison direction logic. It doesn't mention rate limits, pagination behavior, or error conditions, but covers the essential operational 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 in three sentences: purpose statement, parameter requirements, and output format plus authentication. Every sentence earns its place with no wasted words, and key information is front-loaded appropriately.

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 tool with 7 parameters, no annotations, and no output schema, the description provides good coverage of purpose, usage, and behavioral context. It explains what the tool returns (formatted Markdown diff) and authentication requirements. The main gap is lack of explicit guidance on when to use alternatives among sibling tools, but otherwise it's reasonably complete for the complexity level.

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 mentions the three required parameters (workspaceSlug, repoSlug, sinceCommit, untilCommit) but doesn't add meaningful semantic context beyond what's in the schema descriptions. The baseline of 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 between commits') and identifies the resource ('repository identified by workspaceSlug and repoSlug'). It distinguishes from siblings like bb_diff_branches by focusing specifically on commit-to-commit comparison rather than branch comparisons.

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 clear context for when to use this tool ('to compare specific commits') and mentions required parameters. However, it doesn't explicitly state when NOT to use it or name specific alternatives among sibling tools (like bb_diff_branches for branch comparisons or bb_get_commit_history for commit lists).

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