list_folders

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

With no annotations, the description explains that the tool returns a nested tree and supports optional subtree filtering. It is clear that this is a read operation, but does not cover permissions, rate limits, or edge cases.

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 sentences, front-loaded with the core function, and no unnecessary words. Every sentence adds meaningful information.

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?

The description covers the return format (nested tree with fields) and the optional subtree filter. Given no output schema, it provides adequate context for a list tool, though could mention empty results.

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%, but the description adds value by explaining the nested tree structure and the recommendation to use folderId for large projects, clarifying the purpose beyond schema descriptions.

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?

The description clearly states the tool lists folders of a given type as a nested tree, specifying the fields (id, name, parentId, children). It distinguishes from siblings like create_folder (creation) and search_test_cases (search).

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 advises providing folderId for a subtree instead of the full tree, recommended for large projects. It does not explicitly state when not to use or list alternatives, but the guidance is useful.

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