create_branch

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

With no annotations to fall back on, the description carries full responsibility for disclosing behavior. It fails to mention consequences (e.g., if branch exists, overwrite behavior), required permissions, or error conditions. The single clause is overly bare 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?

The description is a single, clear sentence with no redundant words. It front-loads the core action and source reference, achieving high efficiency.

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?

This is a mutation tool with no annotations, no output schema, and only a one-line description. It omits critical context like default behavior (from_branch defaults to default branch, which is only in the schema), potential errors, and safety implications. The description is insufficiently complete for an agent to invoke it confidently in all situations.

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 50% (branch and from_branch have descriptions, repo and owner do not). The description adds no extra semantics beyond the schema; it repeats the source reference concept already present in the from_branch parameter description. At this coverage level, the description should compensate more clearly.

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), the resource (branch), and the source reference type (branch, tag, or SHA). This specific wording differentiates it from other sibling tools and leaves no ambiguity about the tool's function.

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, nor any prerequisites or exclusions. The description merely states the action without contextual cues, leaving the agent to infer applicability.

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