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, it doesn't describe what 'manage' entails operationally: no mention of permissions required, rate limits, whether actions are destructive (e.g., delete_variable), response formats, or error conditions. For a tool with 15 actions and no annotations, this is a significant gap.

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 as a bulleted list which is clear, but it's verbose with 15 bullet points. Some bullets could be grouped (e.g., variable operations). The opening phrase 'Manage Bitbucket Pipelines CI/CD' is front-loaded, but the list format makes it less concise than ideal for an agent.

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 complexity (18 parameters, 15 actions, no annotations, no output schema), the description is incomplete. It lacks critical context: no output information, no error handling guidance, no authentication requirements, and no operational constraints. For a multi-action CI/CD management tool, this leaves the agent with significant uncertainty.

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 18 parameters thoroughly. The description adds minimal value beyond the schema: it maps action names to the 'action' enum but doesn't provide additional context about parameter usage, dependencies, or examples. This meets the baseline for high schema coverage.

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 Pipelines CI/CD' followed by a comprehensive list of 15 specific actions. It distinguishes itself from sibling tools like bitbucket_branches or bitbucket_commits by focusing exclusively on pipeline operations. However, it doesn't explicitly contrast with siblings beyond the domain focus.

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 indicate prerequisites, when certain actions are appropriate, or how this tool relates to sibling tools like bitbucket_repositories or bitbucket_webhooks. The agent must infer usage from action names alone.

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