Bitbucket MCP Server

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool checks configuration status and returns workspace info, but lacks details on what 'configured' means (e.g., authentication, permissions), whether it's a read-only operation (implied but not explicit), error handling, or performance aspects. For a tool with zero annotation coverage, this is insufficient transparency.

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 concise and front-loaded, with the core purpose in the first sentence and return details in the second. Both sentences are relevant, though the second could be integrated more smoothly. There's no wasted verbiage, making it efficient for agent comprehension.

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 low complexity (0 parameters, output schema provided), the description is somewhat complete but has gaps. It covers the basic action and return value, but lacks usage context and behavioral details. With an output schema, it doesn't need to explain return values, but should address when and why to use this tool, especially relative to siblings like 'setup_bitbucket'.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. A baseline of 4 is applied since the schema fully handles parameters, and the description doesn't need to compensate.

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: 'Check if Bitbucket is configured and return current status.' It uses specific verbs ('check', 'return') and identifies the resource (Bitbucket configuration). However, it doesn't explicitly differentiate from sibling tools like 'get_workspace_details' or 'setup_bitbucket', which might have overlapping concerns with configuration status.

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., whether Bitbucket must be set up first), compare to siblings like 'setup_bitbucket' (for configuration) or 'get_workspace_details' (for workspace info), or specify use cases (e.g., diagnostic checks). This leaves the agent without context for tool selection.

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