create_branch

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

With no annotations provided, the description carries the full behavioral burden. It does disclose two useful traits beyond the name: the branch is local (not pushed remotely) and the working tree is switched to it. It says nothing about what happens if the branch already exists, where the branch is created from (current HEAD), or behavior with uncommitted changes — all material for a state-changing git 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, front-loaded with the verb and resource, with no filler. Every clause ('local', 'and switch to') carries distinct meaning.

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 single-parameter tool with no output schema, the description covers the core action and its immediate side effect. However, with zero annotation coverage it should also state failure modes (branch exists, no repo open) and the branch's starting point, which are absent.

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 0%, so the single `branch` parameter is documented only by its name and a minLength constraint. The description adds no guidance on naming conventions, allowed characters or slashes, or whether an existing name is rejected, so it does not compensate for the coverage gap.

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 gives a specific verb (create) plus the resource (a new local branch) and an important secondary effect (switch to it), which an agent cannot infer from the name alone. 'Local' implicitly separates it from push_branch, but no sibling is named explicitly, so it falls just short of full 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?

There is no statement of when to use this versus list_branches, open_repository, or push_branch, and no prerequisites such as needing a repository already open. The only usage signal is the implicit workflow order suggested by 'create and switch'.

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