list_branches

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

readOnlyHint=true already declares the safety profile, so the bar is lower, yet the description adds no behavioral context beyond the bare action itself. It does not mention pagination semantics, ordering, or whether all branches or only the default branch are returned. The content is consistent with the annotation, so there is no contradiction.

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 zero filler — every word earns its place. It is efficient, though so terse that it forfeits the opportunity to add usage or pagination guidance that could have been packed into one more clause.

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?

Given the low complexity, the output schema covers return values and the annotation covers safety, so the one-liner nearly suffices for correct invocation. The clear gaps are pagination defaults and explicit routing guidance to sibling branch tools. For a read-only list operation with this schema richness, the definition is minimally adequate but leaves those decisions to the agent.

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% and the description provides no parameter-level meaning for owner, repo, page, or limit. The conventional GitHub names are partially self-explanatory, but the description does nothing to compensate for the missing schema documentation, such as defaults or interaction of page/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?

The description states a specific verb (list), resource (branches), and scope (in a repository) in six words. It is unambiguous against the branch-related siblings create_branch and delete_branch because the read verb and distinct resource make the intent clear, even though no sibling is named 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 offers no guidance on when to use this tool or when to prefer an alternative. It never contrasts list_branches with create_branch/delete_branch, nor does it place branch listing among the other read tools in the sibling set. Usage context exists only implicitly in the tool name.

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