masscode_list_folders

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

With no annotations provided, the description carries the full burden. It conveys a read-only behavior through the verb 'List' and adds a structural detail ('as a tree structure'), but it does not explicitly state that it is non-mutating, whether authentication is required, or what the exact response shape is. This is adequate for a simple list operation but lacks depth.

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 sentence of eight words, front-loaded with the action and fully informative. Every word earns its place with no redundancy.

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 tool with no output schema, the description covers the core purpose and hints at the return format via 'as a tree structure'. It does not explain whether the tree includes nested folders, sorting, or metadata, but for a simple listing tool this is reasonably complete.

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 input schema has zero parameters, so there is no ambiguity. The description adds no parameter information because none exists. Per the rubric, a zero-parameter tool gets a baseline score of 4, and the description does not detract from this.

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 uses a specific verb 'List' and a clear resource 'snippet folders', with the additional scoping detail 'as a tree structure' that distinguishes it from sibling tools like masscode_create_folder (which creates a folder) and masscode_list_snippets (which lists snippets, not folders).

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—it is for retrieving a hierarchical view of all folders—but it does not explicitly state when to prefer this tool over alternatives such as masscode_create_folder or masscode_list_snippets. The context is clear enough for a simple listing tool, but no exclusions or alternatives are mentioned.

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