git_git_branch_create

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

With no annotations, the description must disclose behavioral traits. It only says 'create a new branch' but does not mention behavior if the branch already exists, whether checkout occurs by default, or any side effects like switching branches. This is minimal transparency.

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 sentence, which is concise, but it lacks essential details like parameter explanations and side effects. It is adequately short but under-specifies, making it minimally viable.

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?

Given the tool has 3 parameters, no annotations, and no description of return values (despite having an output schema), the description is incomplete. It does not cover edge cases, prerequisites, or the meaning of optional parameters, leaving significant gaps for an AI agent.

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 input schema has 0% description coverage for parameters. The description adds only 'from the current HEAD' which gives context for the branch creation but does not explain the purpose of 'name', 'checkout', or 'repo_dir'. The agent gains little insight beyond the schema structure.

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 states 'Create a new branch from the current HEAD,' which specifies the action (create), resource (branch), and source (current HEAD). This distinguishes it from sibling tools like git_git_branch_list or git_git_commit.

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 provided on when to use this tool versus alternatives, such as git_git_branch_list or git_git_commit. There are no prerequisites or conditions mentioned (e.g., repo must exist, no uncommitted changes).

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