bb_get_branches

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the basic action without addressing pagination behavior, rate limits, authentication needs, or response structure, leaving the agent with significant unknowns.

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 a single short sentence, which is concise and front-loaded, but it is under-specified. It omits potentially useful context that could be added without significant verbosity, missing the opportunity to be both brief and 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?

With 6 parameters, no output schema, and no annotations, the description should provide more contextual completeness. It fails to explain pagination behavior, the difference between branches and tags, or what the response contains, making it insufficient for a tool of this complexity.

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?

All six parameters are fully described in the schema (100% coverage), providing clear semantics for workspace, repo_slug, pagination, filtering, and output format. The description adds no extra parameter context, but the schema alone meets the baseline requirement.

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 uses a specific verb and resource ('Get branches for a repository'), accurately stating the tool's purpose. However, it lacks distinguishing details that would set it apart from sibling tools like bb_get_branch, though the name 'branches' already provides some differentiation.

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 such as bb_get_branch for a single branch or bb_get_tags for tags. There is no mention of prerequisites, typical use cases, or conditions that would favor this tool.

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