create_repository_branch

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

No contradiction with annotations: readOnlyHint: false correctly aligns with a create/write operation, and destructiveHint: false is consistent with branch creation. The description adds modest context via 'isolated' and 'run-scoped' but doesn't disclose failure modes (e.g., existing branch name) or whether the operation affects the workspace state.

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?

A single 11-word sentence front-loads the action ('Create an isolated branch') and scopes the resource ('in the run-scoped hosted Git repository'). Every word earns its place; there is no filler or 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?

For a simple create operation with all four required parameters fully documented, annotations present, and an output schema defined, the definition conveys what an agent needs to invoke it correctly. The only notable absence is sibling-routing guidance, which is already accounted for in usage guidelines.

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 100%, so all four parameters are already documented (e.g., 'from' = 'The existing source branch or commit.', 'repository_id' = 'The run-scoped hosted repository ID.'). The description adds no parameter-level meaning beyond the schema, hitting the baseline for high coverage.

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?

States a specific verb ('Create') and resource ('isolated branch in the run-scoped hosted Git repository'), clearly conveying what the tool does. It reads distinctly from sibling list/compare tools by the create verb, but doesn't explicitly name any sibling it is not.

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 phrase 'isolated branch' and 'run-scoped' imply the usage context — creating a run-local branch — but no explicit when-to-use or when-not-to-use guidance is given. With many git-related siblings (list_repository_branches, compare_repository_branches, workspace_git_push_branch), routing is left to inference.

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