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

Annotations declare readOnlyHint=true, which the description does not contradict. The description adds behavioral details beyond annotations: it returns a flat list with parentFolderId and requires project context. Given the readOnly annotation already covers safety, the description provides useful structural insight into the output shape, which is important since there is no output schema.

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?

The description is two short sentences, front-loaded with the core action and output shape, followed by a one-line prerequisite. Every word earns its place; no fluff or redundancy. It is highly efficient for an agent to parse.

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 tool with one parameter, no output schema, and a readOnly annotation, the description covers purpose, output format (flat list, parentFolderId), and the key prerequisite (project context). It does not mention error conditions or what happens without context, but that is a minor gap given the simplicity. It is sufficiently complete for correct invocation.

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%—the folderType parameter description fully explains both 'suite' and 'scenario' values. The tool description essentially repeats this by mentioning 'test suite tree or scenario tree', adding no new semantic detail. 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?

The description states a specific verb ('List'), a clear resource ('folders of the active project's test suite tree or scenario tree'), and adds key details ('flat with parentFolderId per entry'). It clearly distinguishes from generic list_folders by specifying test suite/scenario trees, and from list_test_suites/list_scenarios which return suites/scenarios themselves, not folder structures.

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 implies when to use it—when you need test folder hierarchies—and adds a prerequisite ('Requires project context'). However, it does not explicitly mention alternatives like list_folders or list_test_suites, nor does it state when not to use it. Usage context is clear but not contrasted with siblings.

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