bb_create_branch

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

The description merely restates the mutating action and adds no behavioral context beyond the annotations, such as failure on duplicate branches, required write permissions, or side effects of the default start_point. It does not contradict the annotations, but it contributes little beyond them.

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, compact sentence that front-loads the core action and object with no filler. It earns its place without redundancy.

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 straightforward creation tool with a 100%-described schema and an output schema, the description is mostly sufficient. The only real gap is the absence of when-to-use guidance, which is minor for such a simple operation.

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%, so the schema already documents all four parameters and defaults. The description adds no extra parameter meaning, which places it at the baseline for high 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?

The description names a specific verb and resource: creating a branch in a Bitbucket repository. This clearly separates it from sibling tools like bb_create_repository and bb_create_pull_request. The purpose is immediately understandable.

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?

No guidance is given on when to prefer this tool over alternatives or when not to use it. The description relies entirely on the tool name and the agent's inference from the sibling list, and no prerequisites or exclusions are mentioned.

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