Bitbucket MCP Server

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

No annotations are provided, so the description carries full burden. It states this is a configuration tool but doesn't disclose behavioral traits: whether this persists credentials globally/locally, if it overwrites existing configs, authentication requirements beyond the parameters, error handling, or side effects. 'Configure' implies a write operation, but details are missing.

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 appropriately sized and front-loaded with the core purpose in the first sentence. The Args and Returns sections are structured clearly. However, the 'Returns' section is vague ('Success or error message'), which slightly reduces efficiency.

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 complexity (credential setup with 3 parameters), no annotations, and an output schema exists (though unspecified), the description is moderately complete. It explains parameters well but lacks behavioral context and usage guidelines. The output schema existence means return values needn't be detailed, but more operational info would help.

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 adds substantial meaning beyond the input schema, which has 0% description coverage. It clearly explains each parameter: workspace as 'Bitbucket workspace slug' with an example, username as 'Atlassian account email' with an example, and api_token with a source URL. This fully compensates 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 tool's purpose: 'Configure Bitbucket credentials for the MCP server.' It specifies the action (configure) and resource (Bitbucket credentials), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools, which are all Bitbucket operations but none appear to handle credential setup directly.

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., must be run before other Bitbucket tools), exclusions, or related tools. Given the sibling list includes many Bitbucket operations, this is a significant gap in usage context.

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