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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing: not that this is a read-only operation, not whether it requires project access, not pagination or ordering of branches. The phrasing weakly implies a query of existing state, but no concrete behavioral trait is stated.

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 short and front-loaded, which is good, but its brevity reflects under-specification rather than efficiency—there is no verb, no scope, and nothing an agent can act on beyond the name. It is not bloated, but it fails to earn its place with useful content.

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 tool with no annotations, no output schema, and a single required parameter, the description should at least establish that this is a read of branch refs and what the caller gets back. As written it is too thin to let an agent call it confidently or distinguish it from its git siblings.

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% for the single 'project' parameter, so the schema already documents the input; per the baseline rule this scores 3. The description adds no additional meaning about what 'project' must reference or how it is resolved.

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 is a bare noun phrase with no verb: 'Branches and their head commits.' It restates the tool name (git.branches) and only marginally extends it by mentioning head commits, but an agent cannot tell from this alone whether it lists, reads, or creates branches, nor how it differs from siblings like git.log or git.remote.

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?

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent gets no signal about when git.branches is the right call versus git.log, git.remote, or git.revert.

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