git_checkout

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

Annotations already flag readOnlyHint=false, so the operation is known to be non-read-only, but the description adds no new behavioral context. It does not disclose that switching branches can fail with uncommitted changes, can alter the working directory, or may be rejected by Git in certain states. The description carries the burden and fails to provide this information.

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 extremely concise, with no wasted words, and the core action is front-loaded. While it sacrifices richer context, the two-word phrase is efficient and directly states the primary purpose.

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 state-changing Git operation with no output schema and annotations that only provide false hints. The description is under-specified: it lacks prerequisites, failure conditions, parameter semantics, and any indication of side effects. An agent would not know that checkout may be interrupted by local modifications or that the working tree is affected.

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 was expected to compensate for undocumented parameters. It does not mention repo_path or branch_name at all, and the schema itself only provides type and title, no descriptive text. The parameter names are self-explanatory, but the description adds no meaning beyond the schema.

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 ('switches') and resource (branches), making it clear this tool changes the current branch. It is distinguishable from siblings like git_create_branch or git_branch, though it does not explicitly name alternatives or address checkout's broader file-level behavior.

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 such as git_create_branch or git_reset. There is no mention of prerequisites, scenarios, or caveats like needing a clean working tree, leaving the agent without decision support.

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