gh_create_branch

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the mutating nature is known. The description adds no additional behavioral context: it does not mention whether the branch is checked out, pushed to remote, or what happens if the branch already exists. Beyond stating the core action, it offers no extra transparency.

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 sentence with zero wasted words, front-loaded with the action. It is concise and easy to parse, though it is so brief that it sacrifices informative content. This is still a structurally efficient description.

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 tool with five parameters, a destructive action, and a sibling list, this description is severely under-specified. It does not explain when to use this tool versus alternatives, parameter meaning, or side effects. The output schema exists but does not compensate for the lack of usage and behavioral guidance.

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 0%, so the description must compensate, but it explains none of the parameters. While it implies that 'name' might be the branch name, it does not clarify 'base', 'issue_number', or the roles of owner/repo. The description adds minimal meaning beyond the schema's bare field names.

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 'Create a new branch for an issue' uses a specific verb and resource, clearly distinguishing it from sibling tools like gh_create_pr or gh_create_repo. The phrase 'for an issue' adds context about the association with issue numbers, making the tool's purpose unambiguous.

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 when a branch needs to be created for an issue, but it provides no explicit guidance on when not to use this tool or when to prefer alternatives. No sibling tools are mentioned, and there are no exclusions or prerequisites stated.

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