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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description owes little on the safety front. But it adds nothing at all beyond the name — nothing about pagination, the 50-default/500-max limit, truncation behavior, or empty-repo cases, which are exactly the behaviors an agent needs here.

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?

A single short sentence with zero waste and the core intent front-loaded. Its brevity is achieved by omission rather than by density, so it is concise but thin.

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?

An output schema exists and annotations cover the safety profile, which offloads a lot, and three of four params are documented in the schema. However, for a paged listing tool the absence of any pagination/limit or result-volume note leaves a real gap an agent will hit on large repositories.

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 75%, below the high-coverage baseline, and the one undocumented parameter (limit) is the operationally important one. The description mentions no parameters, so it does not compensate for the gap or explain that results are capped and paginated via limit.

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?

States a specific verb and resource ("List all branches of a repository"), so the operation is unambiguous. It does not distinguish itself from the near-identical siblings ghe_tags_list, bb_branches_list, gl_branches_list, or sq_branches_list; only the tool name/title carries the GitHub Enterprise platform scoping.

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 guidance on when to use this versus the other branch-listing tools or versus ghe_repo_summary. No prerequisites, no exclusions, no mention of what to do when the repo slug is unknown.

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