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

No annotations are provided, so the description carries the full burden, and it does add real behavioral value by disclosing the return fields (path and size) and the ref scoping. However it says nothing about permissions, pagination, or result limits for large repositories, which is a notable gap for a no-annotation tool.

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 sentence with no filler, front-loaded with the verb and resource, and the return fields and scope are packed in without redundancy.

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?

With no annotations and no output schema, the description does convey what comes back (path and size), which helps. But details an agent would want before calling it — large-repo behavior, whether the listing is recursive, permission requirements — are absent.

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%, so ref, prefix, and project are all documented in the schema, making 3 the baseline. The description adds only a slight restatement of the ref semantics ('branch or commit') and never mentions prefix, so it does not exceed the schema.

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 (list), resource (files in the project repo), and even the return shape (path and size), scoped to a branch or commit. It is distinguishable from code.read and code.write by implying directory listing rather than content access, though it never names those siblings.

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?

Usage is implied by the scope ('on a branch or commit', folder filtering) but there is no explicit when-to-use, no exclusions, and no routing to siblings such as code.read for file contents or git.branches for branch enumeration.

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