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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description only adds the path/repo scoping distinction; it says nothing about result truncation or what happens when the limit is hit, which is the main behavioral risk for a repo-wide listing.

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 front-loaded sentence with no filler; the scoping and the downstream purpose both land immediately.

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 4 fully documented params and no output schema, the definition gives enough to call the tool correctly for a read-only listing. What is missing is any hint about the shape or size of the returned tree entries, which would help an agent plan follow-up reads.

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 repo/path/ref/limit are all documented in the schema and the baseline of 3 applies. The description implies the path parameter's meaning ("under one path") but adds no format or default-branch detail beyond 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 and resource ("List the files and folders in a GitHub repository") and scopes it ("whole repo or under one path"), which cleanly separates it from github_get_file (single file read) and github_search (query-based lookup).

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?

"so you can find what to read" tells the agent this is the discovery step that precedes github_get_file, giving clear usage context. It stops short of naming that sibling explicitly or stating any exclusion, so it does not reach a 5.

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