git_create_branch

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: it doesn't say whether HEAD moves to the new branch, what happens if the branch already exists, or whether the working tree is touched — the exact behavioral facts an agent needs for a mutation tool.

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 front-loaded sentence with no filler. It is terse without being padded, though it is arguably under-specified rather than truly concise.

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 non-idempotent mutation with no output schema and two undocumented parameters, the description leaves out the essentials: whether the branch is checked out, behavior on existing branch names, and what the response reports. Only the base_branch semantics are covered, and those come from the schema.

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 coverage is only 33%; base_branch is well documented in the schema, but repo_path and branch_name have no description in either place. The description doesn't compensate — it says nothing about what repo_path should point to or any constraints on branch_name.

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?

States a specific verb+resource (creates a branch) and adds the important detail that the base can be a branch or commit. It doesn't explicitly distinguish itself from siblings like git_branch (likely listing) or git_checkout, leaving that inference to the agent.

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 guidance on when to use this versus git_branch or git_checkout, nor whether the new branch becomes the active one. The agent must guess whether this behaves like 'git branch <name>' or 'git checkout -b'.

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