Bitbucket MCP

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

No annotations are provided, so the description carries full burden. While it lists actions, it doesn't disclose behavioral traits like authentication requirements, rate limits, destructive consequences of delete, pagination behavior, or error handling. The description is functional but lacks operational context.

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?

Well-structured with a brief introductory phrase followed by a bulleted list of actions. Each bullet is clear and specific. The description is appropriately sized for a multi-action tool, though the introductory phrase could be more informative.

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 17 parameters, 7 distinct actions, no annotations, and no output schema, the description is inadequate. It lists actions but doesn't explain return values, error conditions, authentication needs, or how actions differ in behavior. Given the complexity, more contextual information is needed.

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 17 parameters thoroughly. The description adds minimal value beyond implying action-specific parameter relevance (e.g., 'repo_slug required for most actions except list'), but doesn't provide additional syntax, format, or usage details beyond what's in the schema.

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 manages Bitbucket repositories and lists 7 specific actions with verbs and resources. It distinguishes this as a general repository management tool, though it doesn't explicitly differentiate from sibling tools like bitbucket_workspaces or bitbucket_branches beyond scope.

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?

No guidance on when to use this tool versus sibling tools like bitbucket_workspaces or bitbucket_branches. The description lists actions but provides no context about prerequisites, when certain actions are appropriate, or alternatives for similar functionality.

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