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 'Get' operation which implies read-only behavior, but doesn't confirm this explicitly. No information about authentication requirements, rate limits, error conditions, or what happens when parameters are invalid. The description mentions returns 'Step log content' but doesn't describe format, size limits, or potential truncation.

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. The purpose is stated clearly in the first sentence, followed by organized Args and Returns sections. No wasted words or redundant information. While efficient, the Args section could be slightly more detailed given the 0% schema coverage.

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 has an output schema (which handles return value documentation) but no annotations and 0% schema description coverage, the description does an adequate but minimal job. It explains what the tool does and what parameters mean, but lacks behavioral context that would be important for a read operation in a CI/CD context. The presence of an output schema reduces the burden, but more operational guidance would be helpful.

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 schema provides no parameter documentation. The description adds basic semantic context for all 4 parameters, explaining what each represents (repository slug, pipeline UUID, step UUID, workspace). However, it doesn't provide format details, examples, or constraints beyond noting workspace is 'optional if configured'. The parameter explanations are minimal but cover all parameters.

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 with 'Get the log output for a pipeline step' - a specific verb ('Get') and resource ('log output for a pipeline step'). It distinguishes itself from siblings like 'get_pipeline' or 'list_pipeline_steps' by focusing specifically on log retrieval rather than metadata. However, it doesn't explicitly differentiate from potential similar tools not in the sibling list.

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. While siblings include 'get_pipeline' and 'list_pipeline_steps', there's no indication of how this tool relates to them or when an agent should choose log retrieval over general pipeline/step information. The optional workspace parameter gets minimal explanation ('optional if configured'), but no broader usage context is provided.

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