git_git_create_branch

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

No annotations are provided, so the description must disclose behavioral details. It only says 'Create a new branch' without mentioning what happens if the branch already exists, whether it switches to the new branch, or any error conditions. The lack of detail leaves the agent uncertain about side effects.

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 with 8 words, no redundancy, and includes both the action and a usage hint. Every word earns its place.

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 one-parameter tool with an output schema (exists but not described), the description covers the basic purpose and a use case. However, it omits details like error handling, return value, and whether the branch creation switches context. It is adequate but leaves gaps that could affect correct invocation.

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?

With a schema description coverage of 0%, the description should compensate but does not. It only rephrases the parameter name (branch_name) implicitly without adding format, constraints, or examples. For a single required parameter, the description adds no semantic value beyond the schema.

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' and adds context 'useful before experimental changes'. This distinguishes it from siblings like 'git_git_checkout_branch' which switches branches, and 'git_git_list_branches' which lists them. The verb and resource are specific.

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 includes 'useful before experimental changes', implying when to use the tool. However, it does not explicitly mention when not to use it, such as when a branch already exists, or compare it to alternatives like checking out an existing branch. Still, the guidance is clear enough for the intended use.

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