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 at disclosing key behavioral traits. It explains the effect ('marks the pull request as approved'), clarifies the approval's meaning ('indicating that the changes are ready for merge'), mentions return format ('Returns an approval confirmation as formatted Markdown'), and specifies authentication requirements ('Requires Bitbucket credentials with appropriate permissions'). It doesn't mention rate limits or error conditions, but covers the essential mutation 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 in three sentences: the core action with parameters, the effect and meaning, and the requirements. Every sentence earns its place by adding distinct value - operational details, behavioral context, and prerequisites. No wasted words or redundancy.

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 mutation tool with no annotations and no output schema, the description does well at providing essential context. It explains the tool's purpose, behavioral effects, return format, and authentication needs. The main gap is lack of explicit error scenarios or what happens if the PR is already approved, but given the schema's thorough parameter documentation, this is reasonably complete.

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 three parameters thoroughly. The description adds minimal value beyond the schema - it mentions the workspaceSlug default behavior (which is also in the schema) and contextualizes repoSlug as 'containing the pull request.' Since the schema does the heavy lifting, baseline 3 is appropriate.

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 ('approves a pull request'), identifies the resource ('in a repository'), and distinguishes it from siblings like bb_reject_pr and bb_update_pr. It goes beyond just restating the name by explaining what approval means ('marks the pull request as approved... indicating that the changes are ready for merge').

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 about when to use this tool (to approve a pull request) and mentions the optional workspaceSlug parameter with default behavior. It doesn't explicitly state when NOT to use it or name specific alternatives, though the sibling list includes bb_reject_pr as a clear alternative. The guidance is practical but not exhaustive about exclusions.

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