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 for behavioral disclosure. It mentions the tool 'stops' a pipeline (implying a destructive/mutative action) but doesn't describe permissions needed, whether the stop is reversible, rate limits, or what happens to pipeline resources. The return statement is vague ('Confirmation or error message').

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 with a clear purpose statement followed by Args/Returns sections. Each sentence earns its place, though the return statement could be more specific. The formatting helps with readability.

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 destructive operation with no annotations, the description is moderately complete: it explains parameters well and mentions output (though vaguely). However, it lacks critical behavioral context about permissions, reversibility, and side effects that would be important for a 'stop' action.

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 provides meaningful parameter explanations beyond the bare schema: it clarifies what 'repo_slug' and 'pipeline_uuid' represent, notes the UUID format flexibility, and explains the optionality of 'workspace'. This compensates well for the schema's lack of descriptions.

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 ('Stop') and target ('a running pipeline'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'trigger_pipeline' or 'get_pipeline', which would be needed for a perfect score.

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, nor does it mention prerequisites or conditions for stopping a pipeline. It simply states what the tool does without contextual usage information.

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