git_git_checkout_branch

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

No behavioral details beyond the 3-word description. No annotations provided. Does not mention effects on working directory, branch safety, or whether the branch must be fully merged.

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?

Extremely short but at the expense of completeness. The single sentence lacks necessary context, making it under-specified rather than efficiently concise.

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?

Despite having an output schema, the description provides no context on return values, error conditions, or side effects. A checkout operation involves significant state changes left unmentioned.

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 0%. Description does not explain the `branch_name` parameter's role, valid values, or constraints beyond implying it must be an existing branch.

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?

Description clearly states the action (switch) and resource (existing branch), distinguishing it from create/commit/rollback siblings. Could be more specific about what 'switch' entails.

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 on when to use this tool versus alternatives like `git_git_create_branch` or `git_git_commit_all`. No context about prerequisites or when not to use.

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