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 states this is a creation operation but doesn't mention permission requirements, whether the variable is immediately available for pipelines, if there are rate limits, or what happens on duplicate keys. The return statement mentions 'Created variable details or error message' but lacks specifics about format or error conditions.

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 organized Args and Returns sections. Every sentence adds value, though the 'Returns' section could be slightly more specific about what 'details' includes. No redundant information is present.

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 creation tool with no annotations, 0% schema description coverage, but an output schema present, the description does reasonably well. It covers parameter semantics thoroughly and mentions return values generally. However, it lacks important behavioral context about permissions, idempotency, and error handling that would be needed for safe operation.

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 clear semantic explanations for all 5 parameters beyond the 0% schema description coverage. It explains what 'repo_slug', 'key', 'value', and 'secured' mean, notes defaults for 'secured' and 'workspace', and clarifies that 'workspace' is optional if configured. This effectively compensates for the lack of schema 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 ('Create a pipeline variable') and resource ('for a repository'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_pipeline_variables' or explain how this creation differs from other variable-related operations that might exist.

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., needing repository access), compare with sibling tools like 'list_pipeline_variables', or specify scenarios where creating a pipeline variable is appropriate versus other configuration methods.

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