Bitbucket MCP Server

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

No annotations are provided, so the description carries the full burden. It states the action is a deletion but doesn't disclose critical behavioral traits such as whether deletion is permanent/reversible, permission requirements, side effects, or rate limits. This is inadequate for a destructive operation.

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 and front-loaded with the core purpose, followed by structured parameter and return sections. Every sentence earns its place, though the 'Returns' line could be more specific.

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 destructive nature, lack of annotations, and an output schema (implied by 'Has output schema: true'), the description is moderately complete. It covers parameters and basic purpose but misses behavioral context and detailed usage guidelines, which are crucial for a deletion tool.

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?

With 0% schema description coverage, the description compensates by explaining all three parameters: 'repo_slug' (repository slug/name), 'name' (tag name to delete), and 'workspace' (optional Bitbucket workspace). It adds meaning beyond the bare schema, though it could detail format constraints.

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 ('Delete a tag') and resource ('from a repository'), distinguishing it from sibling tools like 'create_tag' or 'list_tags'. It uses precise terminology that aligns with the tool's name without being tautological.

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 no guidance on when to use this tool versus alternatives like 'delete_branch' or 'delete_repository', nor does it mention prerequisites or context for deletion. It lacks explicit when/when-not instructions or named alternatives.

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