get_storage_folders_tree

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

No annotations are provided, so the description carries the burden. It only states what the tool does, not behavioral details like whether it includes empty folders, pagination, depth limits, or the exact structure of the returned tree. Minimal extra transparency is offered.

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 a single, clear sentence with no unnecessary words. It is front-loaded and entirely earned.

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 zero-parameter read tool, the description is fairly complete: it names the resource and the tree format. However, without an output schema, more detail about the return structure (e.g., nested objects, included fields) would be helpful. Still, the simplicity of the tool means this is adequate.

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?

The tool has zero parameters, so the schema fully covers parameters. The description adds no parameter details, but with no params to document, a baseline of 4 is appropriate per the rubric.

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 retrieves storage folders as a tree hierarchy, using a specific verb and resource. This distinguishes it from sibling tools like list_storage_folders (flat list) and get_storage_folder (single folder).

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 usage when a tree structure is needed, but does not explicitly contrast with list_storage_folders or get_storage_folder. No when-to-use or when-not-to-use guidance is provided, though the tree wording offers some context.

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