git_branch_create

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

Annotations already state this is not read-only, not destructive, not idempotent, and closed-world. The description adds a valuable safety guarantee beyond annotations: it never overwrites an existing branch, and it clarifies the optional switch behavior.

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?

Two short sentences with zero wasted words; the core action and the key safety constraint are front-loaded.

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?

An output schema exists and annotations cover the safety profile, but the description is still thin for a four-parameter tool with 0% schema coverage. It leaves start_point and repo behavior unexplained, which matters for 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?

Schema description coverage is 0%, so the description must compensate for four undocumented parameters. It mentions only branch creation and implies the switch parameter, but says nothing about name requirements, start_point semantics, or the repo parameter.

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 states a specific verb and resource: create a new branch, with optional switching. It also clarifies the non-overwrite behavior, which distinguishes it from a generic branch operation, though it does not explicitly name sibling tools like git_switch.

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?

It implies usage when a new branch is needed and notes switching can be optional, but it gives no explicit guidance on when to use this versus git_switch, nor any prerequisites such as clean working tree or permissions.

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