Bitbucket MCP

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. While it lists actions (create, update, delete), it doesn't disclose important behavioral traits: required permissions, whether operations are destructive, rate limits, authentication needs, error handling, or what happens when webhooks are deleted. The description is purely functional without behavioral 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 structured with a clear opening statement followed by a bulleted list of actions. However, it's somewhat repetitive (listing both repository and workspace versions of each action) and could be more efficiently organized. Every sentence earns its place but could be more concise.

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 complexity (12 parameters, multiple actions, no annotations, no output schema), the description is inadequate. It doesn't explain return values, error conditions, authentication requirements, or operational constraints. For a tool with this many parameters and actions, the description should provide more contextual guidance about how to use it effectively.

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 100% schema description coverage, the schema already documents all 12 parameters thoroughly. The description adds no parameter semantics beyond what's in the schema - it doesn't explain parameter relationships, dependencies, or provide examples. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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: 'Manage Bitbucket webhooks for repositories and workspaces' with a specific list of actions. It distinguishes from siblings by focusing on webhooks rather than branches, commits, issues, etc. However, it doesn't explicitly differentiate from potential overlapping tools (like general repository management).

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. It lists actions but doesn't explain when to choose repository-level vs workspace-level webhooks, or when to use this tool versus other Bitbucket tools. There's no mention of prerequisites, dependencies, or typical use cases.

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