Bitbucket MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals this is a read operation (implied by 'List'), includes pagination behavior with defaults, and mentions the maximum pagelen of 100. However, it doesn't disclose important behavioral aspects like rate limits, authentication requirements, error conditions, or what happens when workspace is null. The description adds some value but leaves significant gaps for a tool with no annotation coverage.

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 with clear sections (Args, Returns) and efficiently conveys essential information. The main purpose is stated upfront, followed by parameter details. While concise, it could be slightly more front-loaded by mentioning pagination in the opening sentence to better set expectations.

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 that this is a read operation with an output schema (which handles return value documentation), the description is reasonably complete. It covers all parameters and basic behavior. However, for a tool with no annotations and 3 parameters, it should ideally include more about authentication, error handling, and the implications of the optional workspace parameter to be fully complete.

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?

With 0% schema description coverage, the description compensates well by explaining all three parameters. It clarifies that 'workspace' is optional if configured, 'page' defaults to 1, and 'pagelen' defaults to 25 with a maximum of 100. This adds meaningful context beyond what the bare schema provides, though it doesn't explain the format or validation rules for the workspace parameter.

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 action ('List') and resource ('projects in a workspace'), making the purpose immediately understandable. It distinguishes itself from siblings like 'get_project' (singular) and 'list_workspaces', though it doesn't explicitly contrast with other list tools like 'list_repositories'. The description is specific but could be more distinctive among similar list operations.

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 when this tool is appropriate compared to 'list_workspaces' or 'get_project', nor does it specify any prerequisites or context for usage. The optional workspace parameter is noted but without explanation of when it's needed versus when it can be omitted.

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