Bitbucket MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination behavior (page/pagelen parameters) and that it returns a list of pipelines with details, which is helpful. However, it doesn't disclose critical behavioral traits such as whether this is a read-only operation (implied but not stated), rate limits, authentication requirements, error conditions, or what specific details are included in the returned list. For a tool with no annotation coverage, this leaves significant gaps.

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 opening sentence followed by organized sections for 'Args' and 'Returns'. It's appropriately sized with no redundant information. However, the 'Args' section could be slightly more concise by integrating some details into the opening sentence, and the 'Returns' section is somewhat vague ('with their details').

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 moderate complexity (5 parameters, 1 required), no annotations, and the presence of an output schema, the description does a good job. It thoroughly documents parameters and mentions the return type. The output schema existence means the description doesn't need to detail return values. However, it lacks context about authentication, error handling, and explicit read-only confirmation, which would make it more complete for a tool with no annotations.

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?

The description provides excellent parameter semantics beyond the input schema, which has 0% description coverage. It clearly explains each parameter's purpose: 'repo_slug' as the repository name, 'sort' with an example ('-created_on'), 'workspace' context, and pagination details ('page' and 'pagelen' with defaults and max value). This fully compensates for the schema's lack of descriptions and adds practical usage context.

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 verb ('List') and resource ('pipelines for a repository'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'get_pipeline' (which retrieves a single pipeline) and 'list_pipeline_steps' (which focuses on steps within a pipeline). However, it doesn't explicitly mention that this lists ALL pipelines or specify any inherent filtering beyond what parameters allow.

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 doesn't mention sibling tools like 'get_pipeline' (for single pipeline details) or 'list_pipeline_steps' (for pipeline components), nor does it specify prerequisites such as authentication or repository access requirements. The only implied context is that it operates on a repository.

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