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

Annotations only declare readOnlyHint=true, so the description carries the rest and does it well: it discloses the 500-entry cap, the 1-4 level depth window, that results are truncated when cut off, and that a resolved sha is returned. These are genuine behavioral traits beyond the annotation, though nothing is said about pagination or error/auth behavior.

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?

Two dense sentences, front-loaded with the operation and followed by the operational limits. Every clause carries information (entry cap, depth, truncation, returned sha) and there is no filler.

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 output schema, the description responsibly mentions the returned resolved sha, plus the truncation and depth constraints an agent needs to interpret results. It is close to complete for a read-only listing tool, missing only pagination and any hint about error conditions.

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 the schema already documents ref, path, depth, and repositoryID. The description restates the ref and depth semantics ('at a ref', '1-4 levels below path') without adding syntax or format details the schema lacks, which is the baseline-3 case.

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 (Lists) and resource (a repository directory at a ref), which is enough to tell it apart from repo_file, repo_blame, or repo_history by resource type. It does not explicitly name any sibling, so it stops short of a 5.

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 when-to-use, when-not-to-use, or alternative routing guidance. With siblings like repo_search, repo_file, and repo_context available, an agent gets no help deciding when a directory listing is the right call versus those tools.

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