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 of behavioral disclosure. It mentions that the tool 'Creates a webhook' and returns 'Created webhook details or error message', but lacks details on permissions required, rate limits, whether the webhook is immediately active, or how errors are handled. This leaves significant gaps for a mutation tool.

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 is appropriately sized with no redundant sentences, though the 'Args' section could be slightly more concise by integrating some details into the main description.

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 that there is an output schema (which handles return values), the description does not need to explain returns in detail. However, as a mutation tool with no annotations and 6 parameters, the description should provide more behavioral context (e.g., authentication needs, error conditions). The parameter explanations are good, but overall completeness is moderate due to missing operational details.

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 6 parameters in the 'Args' section, adding meaning beyond the bare schema. It clarifies optional vs. required parameters, provides examples for 'events', and notes defaults for 'active' and 'workspace'. However, it doesn't specify format constraints (e.g., URL validation) or event enum values.

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 action ('Create a webhook') and the target resource ('for a repository'), making the purpose specific and unambiguous. It distinguishes itself from sibling tools like 'delete_webhook' and 'list_webhooks' by focusing on creation rather than deletion or listing.

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 when needing to set up a webhook for repository events, but does not explicitly state when to use this tool versus alternatives like 'list_webhooks' for checking existing webhooks or 'delete_webhook' for removal. No exclusions or prerequisites are mentioned, leaving usage context partially inferred.

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