Bitbucket MCP

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 but provides minimal information. It lists actions but doesn't describe what each action actually does, their side effects, permission requirements, rate limits, or response formats. For example, 'delete' implies destructive action but with no warnings or confirmation details.

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 efficiently structured with a brief purpose statement followed by a bulleted list of actions. Every line serves a purpose with zero wasted words. However, the bulleted format could be more front-loaded with critical usage information rather than just listing actions.

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 complex tool with 16 parameters, 11 distinct actions, no annotations, and no output schema, the description is inadequate. It doesn't explain action behaviors, return formats, error conditions, or authentication requirements. The agent would struggle to use this tool correctly without significant trial and error or external documentation.

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 100%, so the schema already documents all 16 parameters thoroughly. The description adds no parameter-specific information beyond the action list. The baseline of 3 is appropriate since the schema does the heavy lifting, though the description could have explained parameter dependencies (e.g., which parameters apply to which actions).

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: 'Manage Bitbucket issue tracking' with a comprehensive list of 11 specific actions. It distinguishes this tool from siblings like bitbucket_branches or bitbucket_pull_requests by focusing exclusively on issue operations. However, it doesn't explicitly contrast with sibling tools beyond the domain difference.

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. There's no mention of prerequisites, authentication requirements, or which actions are appropriate for different scenarios. The list of actions implies usage contexts but offers no explicit guidance on selection criteria or trade-offs.

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