list_branches

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return content (names, latest commits, default-branch identification), which is genuinely useful. But it says nothing about pagination behavior, permissions/scopes required, or that the operation is strictly read-only — modest disclosure for a zero-annotation tool.

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?

Two sentences, zero waste. The action and scope are front-loaded in sentence one and usage contexts follow in sentence two. Nothing is padded or redundant.

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?

There is no output schema, so the description usefully compensates by summarizing the returned data (branch names, latest commits, default branch marker). Combined with 100%-covered parameters, an agent has enough to call it. It falls short of 5 only because pagination/return-shape details and any auth prerequisites are left implicit.

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%, with all five parameters (limit, start, project, filterText, repository) documented inline including defaults and env-var fallbacks. The description adds no additional parameter meaning beyond the schema. Baseline 3 is appropriate when the schema does all the work.

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?

States a specific verb and resource ('List branches in a Bitbucket repository') and goes further to enumerate what the listing contains: branch names, latest commits, and the default branch. An agent can immediately distinguish this from list_commits, delete_branch, or browse_repository without inspecting the schema.

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 second sentence gives concrete usage contexts: 'explore available branches, find branch names for checkout or PR creation, or verify branch existence before operations.' This is clear when-to-use guidance. It does not, however, name an alternative or state exclusions (e.g. when to prefer list_commits or browse_repository instead), so it stops short of a 5.

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