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

With no annotations, the description carries the full burden and does real work: it discloses the listing is capped and that truncated=true signals dropped entries, plus the memory:read requirement and that binding errors mirror github_repo_get. It still doesn't say how large the cap is or whether to re-query with a narrower path when truncated.

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?

Three short sentences, zero filler, and the core behavior plus the truncation caveat are front-loaded before the prerequisite details. Every sentence supplies information an agent could act on.

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 simple read tool with an output schema and fully documented params, the description covers the two non-obvious things: silent truncation and the auth/binding prerequisites. The one remaining gap is the absence of cap size or a recovery instruction when truncated is true.

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 coverage is 100%, so ref, path and github are already documented in the schema. The description adds no path/ref semantics of its own, so baseline 3 applies.

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 one directory of a connected repo') and the 'one directory' scoping implicitly separates it from github_file_get and recursive listing behavior. It does not name a sibling tool explicitly, so differentiation is inferential rather than stated.

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: the agent learns it lists a single directory level, not a recursive tree, and that github_file_get handles single files. No explicit when-to-use/when-not or alternative routing is given, and nothing tells the agent when to prefer github_code_search or github_repo_get instead.

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