create_branch

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds that existing branches are never overwritten, which is meaningful non-destructive context. However, it doesn't disclose behavior around failed creation (does it error or no-op if branch exists?), or any permission/auth requirements. With sparse annotations, the description could add more.

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 concise sentences, no filler. The second sentence about not overwriting is valuable. Efficient and 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?

For a create operation with no output schema and sparse annotations, the description is adequate but thin. It covers the core purpose and one safety guarantee, but lacks detail on return values, error cases (branch already exists), and the relationship between branch and sourceBranch parameters.

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 20% (only 'repository' has a description). The description mentions 'from an existing branch' implicating sourceBranch but doesn't explain the default behavior of sourceBranch defaulting to 'main'. The description adds minimal value over the schema for the parameters.

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 action: 'Create a feature branch from an existing branch.' This is a clear verb+resource with a scope qualifier ('feature branch'). It distinguishes reasonably from sibling tools like get_branch and create_repository, though it doesn't name them explicitly.

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?

The description implies usage (creating branches) but provides no explicit when/when-not guidance or comparison to alternatives. The 'Existing branches are never overwritten' sentence is more of a safety note than usage guidance.

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