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') and optional parameters, which is helpful. However, it doesn't cover critical aspects like authentication requirements, rate limits, error conditions, or whether it's a read-only operation (though 'List' implies safety). For a tool with no annotations, 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 and appropriately sized. It front-loads the purpose, then details args and returns in clear sections. Every sentence adds value, with no redundancy. It could be slightly more concise by integrating the args into the main flow, but it's efficient overall.

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 (4 parameters, 1 required), no annotations, and an output schema present, the description is reasonably complete. It covers the purpose, parameters, and return type. The output schema handles return values, so the description doesn't need to detail them. However, it lacks behavioral context like auth or errors, keeping it from a 5.

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 0%, so the description must compensate. It adds meaningful semantics for all four parameters: 'repo_slug' as repository name, 'workspace' as optional Bitbucket workspace, and pagination details with defaults and constraints ('max 100'). This goes well beyond the bare schema, though it doesn't explain format specifics (e.g., slug format).

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: 'List pipeline variables configured for a repository.' It specifies the verb ('List') and resource ('pipeline variables'), and distinguishes it from sibling tools like 'create_pipeline_variable'. However, it doesn't explicitly differentiate from other list tools (e.g., 'list_pipelines'), so it's not a perfect 5.

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 prerequisites (e.g., authentication), compare it to other list tools, or specify scenarios where it's appropriate. The optional 'workspace' parameter hint is minimal context, not explicit usage guidelines.

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