bitbucket_branch_list

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, non-mutating read operation, and the description ('List') is consistent with those. The description adds no additional behavioral context such as pagination, ordering, or output scope, but the annotated safety profile lowers the burden here.

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?

A single front-loaded sentence with no filler, repetition, or unnecessary words. Every word carries meaning and the core action is immediately visible.

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?

This is a minimum-viable description: it names the operation and relies on the schema for parameter semantics and on annotations for safety. It lacks guidance on pagination/limits, output shape, and when to use it relative to sibling list tools, which is a clear gap for a tool with no output schema.

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 coverage is 50%, with query and workspace already described in the input schema; repoSlug and maxItems have no description but are semantically obvious from their names and constraints. The description itself adds no parameter detail beyond tying the operation to 'a repository', so it does not materially improve on 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 uses a specific verb ('List') and resource ('branches in a repository'), clearly identifying what the tool does. It does not explicitly distinguish itself from sibling tools like bitbucket_tag_list or bitbucket_commit_list, but the resource is specific enough on its own.

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 choose this tool over alternatives such as tag_list or commit_list, and it does not mention prerequisites like requiring a workspace or repoSlug. Usage context is only implied by the tool name and schema.

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