List branches

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond that baseline — no mention of pagination limits, result ordering, or what happens with an invalid repo path. With annotations doing all the work, the description contributes no behavioral context.

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?

It is a single front-loaded sentence with zero wasted wording, which is good structurally. However, the brevity stems from under-specification rather than efficiency — there is no second sentence because nothing substantive was said.

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 paginated listing tool with no output schema, the description should at least note pagination behavior or the shape of results (branch names, default page size). It says nothing about return values or how to handle large branch lists, leaving real gaps for an agent planning the call.

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%, and the schema documents repo format, page numbering, and page_size limits thoroughly. The description adds no meaning beyond the schema, but per the high-coverage baseline a 3 is appropriate since the schema carries parameter semantics.

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?

"List branches of a repository" essentially restates the tool name (repo_branch_list) and title (List branches) with no additional specificity. It does not distinguish this tool from siblings like repo_branch_get, repo_tag_list, or repo_tree_list, so an agent learns nothing beyond the name itself.

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 call this versus repo_branch_get (single branch details) or repo_tag_list, and no mention of prerequisites such as needing a valid repo path or pagination for large result sets. The agent must infer all usage context from the name alone.

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