bb_create_branch

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 clearly states the core mutation, but it does not disclose permission requirements, behavior when the branch already exists, whether the operation is idempotent, or what the response looks like. This is a significant gap for a write operation.

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?

One sentence with no filler; the essential verb, object, and source qualifier are front-loaded. Every word contributes.

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 simple create-branch operation, the required parameters are all present and the core behavior is clear, but with no annotations and no output schema the description leaves out error conditions, default-branch nuance, and response shape. It is minimally viable but not 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?

The description ties 'given start point' to the optional start parameter and 'new branch' to branch, but this largely repeats the schema's existing descriptions. It adds no explanation for the undocumented projectKey and repoSlug parameters, so it only partly compensates for the 50% schema coverage.

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 ('Create') and resource ('new branch') plus the start point, so an agent can identify it as the branch-creation tool and distinguish it from bb_list_branches, bb_get_branch, and bb_delete_branch.

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 action 'Create' implies the appropriate use case, and the start-point qualifier provides context, but the description does not explicitly state when to prefer it over related operations or mention prerequisites such as repository write access. The guidance is implied rather than explicit.

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