Bitbucket MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses the tool's read-only nature implicitly through 'Get', but lacks details on permissions required, rate limits, error conditions, or pagination. The return format is described, adding some behavioral context, but critical operational traits are missing.

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 well-structured with a clear purpose statement followed by Args and Returns sections. It's appropriately sized with no redundant information, though the 'Args' and 'Returns' labels could be integrated more seamlessly into the flow.

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 (2 parameters, read-only operation), the description is reasonably complete. It covers purpose, parameters, and return values. With an output schema present, detailed return explanations are unnecessary. However, it lacks context on authentication needs or error handling, leaving minor gaps.

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 explains the meaning of 'repo_slug' as 'Repository slug (name)' and 'workspace' as 'Bitbucket workspace (optional if configured)', adding semantic clarity beyond the bare schema. However, it doesn't detail format constraints (e.g., slug patterns) or default behaviors when workspace is omitted.

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') and resource ('default reviewers configured for a repository'), distinguishing it from sibling tools like 'add_reviewer' or 'remove_reviewer'. It precisely defines what the tool retrieves without ambiguity.

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 default reviewers, but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'get_user_permissions' for reviewer permissions) or prerequisites. It mentions the workspace parameter is optional 'if configured', which offers some contextual hint but not comprehensive alternatives.

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