list_branches

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered without the description. The one genuine addition is that name_filter matches the start of the branch name (prefix, not substring), which an agent could not infer from the schema. Nothing is said about result volume, pagination, or default-branch inclusion, so it stays at adequate rather than rich.

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 compact clause pair with no filler, and the most decision-relevant fact (prefix matching) is placed inline where it is needed. It is terse to the point of under-specification, but that is penalized under other dimensions rather than for verbosity here.

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 so return values need no explanation, but for a three-parameter tool with zero schema description coverage the description leaves too much unstated, notably the meaning of project versus repository and the scope of what is listed. An agent can guess, but the definition does not make correct invocation self-evident.

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 carry the parameter burden, and it only explains name_filter's prefix-matching behavior. The critical project vs repository distinction (project is optional and nullable, repository is required) is left entirely unexplained, as is what form each identifier takes.

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 names the concrete resource (branches of a repository) and the sibling set supports that reading, distinguishing it from list_repositories, list_commits, and browse_repository. It is a noun phrase rather than a verb+resource statement, but the tool name supplies the verb and the resource 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?

There is no guidance on when to call this instead of browse_repository or list_commits, no mention of prerequisites, and no note on whether all branches or only some subset are returned. The only usage-adjacent hint is the name_filter prefix semantics, which describes a parameter rather than tool selection.

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