create_branch

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

The annotation indicates a write operation (readOnlyHint=false), and the description adds critical safety behavior: 'dry_run=true by default.' The parameter schema further explains that false requires user confirmation, providing transparency beyond the annotation without contradiction.

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 front-load essential information: the action and the default behavior. Every word is necessary; no redundancy.

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?

No output schema is provided, and the description omits return value details. For a creation tool, mentioning that a branch object is returned would be helpful. However, the dry_run behavior is well-covered, partially compensating.

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 100%, so the baseline is 3. The description does not add new information beyond the schema's detailed parameter descriptions, which already explain the 'dry_run' behavior and required fields.

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 the action ('Create a new branch') and the source ('from a ref'). It is specific and unambiguous, distinguishing it from sibling tools that involve different actions (e.g., merge, commit, list).

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 like merge_merge_request or list_branches. There is no mention of prerequisites or when not to use it, leaving the agent to infer context.

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