list_folders

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

No annotations are provided, so the description must carry full behavioral disclosure, but it only says 'lists the folders.' It does not clarify whether nested folders are included, whether all accounts are covered when account_id is null, whether there is a default account, or whether the operation has any side effects.

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, front-loaded sentence with no filler words. For a simple list operation, this is concise and structurally appropriate, although other dimensions capture its lack of supporting details.

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?

This is a simple read-only list tool with one optional parameter and an output schema, so an exhaustive description is not required. However, the description is only minimally complete: it leaves unresolved the meaning of account_id and whether omitting it targets the current/default account.

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 0%, and the description does not mention the account_id parameter at all. The agent cannot infer the meaning, default behavior, or optionality without additional context, making the parameter semantics effectively undocumented.

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 and resource ('Elenca le cartelle' = lists the folders) and scopes it to the account. This clearly identifies the operation and naturally distinguishes it from sibling folder actions such as create_folder and delete_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 gives no guidance on when to use this tool versus alternatives, when to supply account_id, or how it relates to list_accounts or other folder operations. It only states what the tool does, so the agent receives no explicit selection support.

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