Atlassian 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 effectively describes the operation's purpose, return format ('raw content of the file as text'), and authentication requirement ('Requires Bitbucket credentials'). However, it doesn't mention potential error conditions, rate limits, file size limitations, or encoding considerations that would be helpful for an agent.

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 in three sentences: the core purpose, parameter usage with optional behavior, and return format plus authentication requirement. Every sentence adds essential information with zero wasted words, making it easy for an agent to parse quickly.

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 read-only file retrieval tool with no annotations and no output schema, the description provides good coverage of the operation's purpose, parameters, return format, and authentication needs. The main gap is the lack of output schema, which means the agent doesn't know the exact structure of the returned content, though 'raw content as text' gives reasonable guidance.

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 100% schema description coverage, the schema already documents all four parameters thoroughly. The description adds minimal value beyond the schema by briefly mentioning the optional 'revision' parameter and its default behavior, but doesn't provide additional semantic context or examples beyond what's in the schema 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 specific action ('Retrieves the content of a file'), identifies the resource ('from a Bitbucket repository'), and distinguishes it from siblings by focusing on file content retrieval rather than repository metadata, PR operations, or other repository actions listed in the sibling tools.

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 clear context for when to use this tool (to retrieve file content) and mentions an optional parameter (revision) with its default behavior. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools for different scenarios.

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