gitlab_add_branch

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a branch is created and identifies the HTTP method; it does not mention side effects, required permissions, idempotency, or error behavior such as what happens if the branch already exists.

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 short, front-loaded sentence with no filler. The parenthetical endpoint adds useful precision without repeating schema information or wasting words.

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 mutating tool with no annotations and no output schema, the description is too sparse. It omits what a successful response looks like, behavior on conflicts, prerequisites such as project existence or permissions, and any post-condition details. The schema covers the parameters but not the operational context.

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 67%, so ref and projectId are partially explained by the schema, but the description adds no parameter-level meaning. The 'branch' parameter has no schema description and the tool description does not explicitly clarify that it is the new branch name, leaving an ambiguity that the description fails to resolve.

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 starts with a specific verb and object, 'Creates a branch,' and adds the exact REST endpoint 'POST /repository/branches', making the tool's purpose unambiguous. It is clearly distinct from sibling GitLab tools such as gitlab_add_commit or gitlab_create_issue, none of which create branches.

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?

Usage is only implied: an agent can infer this tool is for creating a new branch in a GitLab project, but there is no explicit guidance on when to use it versus alternatives, nor any mention of preconditions or limitations. No exclusions or alternative tools are noted.

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