create_branch

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

No annotations are supplied, so the description carries the full disclosure burden and falls well short. It does not say whether the call fails if the branch already exists, whether it is idempotent, what permissions or write access are required, or whether branch protection applies — all critical 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?

It is a single front-loaded sentence with no filler, which is structurally clean. However, for a 5-parameter mutation tool with no annotations, that brevity reads as under-specification rather than efficient conciseness.

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?

A write operation with no annotations, no output schema, and five parameters gets only one sentence, leaving the agent without expected return values, error conditions, or side effects. The rich schema descriptions compensate partially, but the description itself is inadequate for the tool's complexity.

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 100% and the schema even documents the refs/heads naming convention and an example, so the description needn't repeat parameter details. The description adds no meaning beyond the schema, making the baseline 3 appropriate.

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 branch) plus the origin (from an existing one), so the operation is unambiguous. Siblings contain no other branch-creation tool, so no explicit differentiation is needed, but the branch is implicitly a repository branch only because the schema says so, not the description.

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 when-to-use / when-not-to-use guidance: nothing about when to branch versus committing to an existing branch, no prerequisite that the source branch must exist, and no mention that this pairs with create_pull_request for new-branch workflows. The only procedural hint (refs/heads formatting) lives in the schema, not the description.

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