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 for behavioral disclosure. It states the tool returns 'diff content as text', which is useful, but lacks critical details: whether this is a read-only operation, any rate limits, authentication requirements, error conditions, or format specifics (e.g., unified diff). For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 clear purpose statement followed by well-organized Args and Returns sections. Every sentence earns its place by providing essential information without redundancy. The formatting with bullet-like sections enhances readability while maintaining brevity.

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 has output schema), the description is reasonably complete. The output schema exists, so the description doesn't need to detail return values beyond stating 'diff content as text'. It covers parameter semantics well despite 0% schema coverage. However, the lack of behavioral context (especially with no annotations) prevents a perfect score.

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 provides clear semantic explanations for all three parameters: repo_slug as 'Repository slug (name)', spec as 'Commit hash or range' with examples, and workspace as 'Bitbucket workspace (optional if configured)'. This adds substantial value beyond the bare schema, though it doesn't cover all possible edge cases (e.g., format of repo_slug).

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 specific action ('Get the diff') and resource ('for a commit or commit range'), distinguishing it from siblings like get_commit (which retrieves commit metadata) or get_pull_request_diff (which focuses on pull requests). The verb+resource combination is precise and unambiguous.

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 for retrieving diff content from commits, but provides no explicit guidance on when to choose this over alternatives like get_commit_diffstat (for statistics) or get_pull_request_diff (for pull request diffs). It mentions the workspace parameter is optional if configured, which offers some context but doesn't address tool selection.

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