list_branches

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

No annotations are provided, so the description carries the full burden. It discloses no behavioral traits — no mention of pagination behavior, whether it lists local or remote branches, sorting, rate limits, or what the response contains. For a read tool with zero annotations, this is a gap.

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?

Two-word description is extremely concise with zero waste. However, this borders on under-specification rather than genuine conciseness — it's short because it says almost nothing, not because it efficiently conveys a full picture.

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?

There is an output schema and 3 parameters, but the description explains none of the parameter semantics and only vaguely the purpose. For a tool with zero schema description coverage and no annotations, it should carry far more explanatory weight than it does. The agent can only guess at branching behavior and parameter format.

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 must add meaning to the 3 parameters. It does not explain 'repo', 'owner', or 'max_items' at all. An agent would not know how owner/repo combine, what max_items controls, or the required format.

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 says 'Lists repository branches' — clear verb+resource, but terse. It doesn't distinguish from siblings like list_pull_requests or the preview functions, though the resource (branches) is unambiguous.

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 vs alternatives. No mention of the owner param (which appears optional with a default), or how it relates to inspecting remote branches. No exclusions or comparisons with sibling tools.

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