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

Annotations already mark readOnlyHint=true, covering the safety profile. The description adds useful behavioral context: the tree is capped at top 3 levels, and the returned paths are directly compatible with read_files and apply_changes, revealing both a depth limitation and the output's downstream contract. No contradiction with annotations.

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 tightly constructed sentences with no filler. The core purpose and depth limit are front-loaded, and the path-compatibility detail clearly earns its place by connecting to sibling tools.

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 one-parameter, read-only, output-schema-backed tool, this description is sufficient: it states the depth limit and the output's downstream use. The annotations cover safety, and the output schema covers return format, so nothing essential is missing.

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%: project_name is described as 'Name of the project'. The description adds no additional parameter-level guidance (e.g., where to obtain a valid project_name), but with full schema coverage the baseline of 3 is appropriate.

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 clear verb ('List'), resource ('a project's files and folders'), and a scope ('top 3 levels'). It explicitly ties the output to the exact paths accepted by read_files and apply_changes, distinguishing it from sibling tools like list_projects and read_files.

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?

The description doesn't explicitly enumerate when to use or avoid alternatives, but it establishes clear context: the output is defined as the exact paths read_files and apply_changes take, implying this tool is the prerequisite for those operations. It lacks explicit exclusions, hence not a 5.

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