Git branches

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

The annotations already declare readOnlyHint=true, and the description consistently describes a listing operation. It adds useful behavioral context beyond the annotation by specifying that both local and remote branches are listed and that the repository is on the host, implying a local filesystem operation rather than an API call.

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, front-loaded sentence with no filler. Every word contributes meaning: it states the action, scope (local and remote), resource (branches), and context (repository on the host).

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 simple read-only listing tool with one parameter, readOnlyHint=true, and an output schema. The description covers what the tool does and where it operates. There is no missing information needed for an agent to select and invoke it correctly.

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?

The input schema has 0% description coverage for its single required parameter, so the description must compensate. It does so by indicating that the repository is on the host, which tells the agent that 'path' refers to a local Git repository path. It does not provide detailed path formatting guidance, but for a single obvious parameter this is sufficient.

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 uses a specific verb and resource: 'List local and remote branches for a repository on the host.' It clearly identifies what the tool does and distinguishes it from sibling git tools like git_tag (tags), git_log (history), and git_status (working tree state) by naming branches explicitly.

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 when to use the tool: when the agent needs to see local or remote branches. However, it does not explicitly mention alternatives or exclusions, even though many related git sibling tools exist. The usage context is clear but not fully elaborated.

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