delete_folder

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It hints at a two-phase process ('due fasi') but does not explain what that entails—whether deletion is permanent, reversible, or has side effects. No caveats about permissions or cascading behavior are given.

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 extremely concise and front-loaded with the verb and object. Every word earns its place, though the cryptic 'due fasi' is additional information that could confuse without elaboration. Still, brevity is a strength here.

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 deletion tool with three parameters and no output schema or annotations, this description is severely under-specified. It fails to explain the two-phase behavior, parameter roles, or any consequences of deletion. Agents cannot safely invoke this tool based on the information provided.

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 explain the parameters. While folder_id is self-explanatory, account_id and request_id are entirely opaque. The description adds no value over the raw schema, leaving parameter roles unclear.

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 action ('Elimina' = deletes) and the resource ('cartella' = folder), distinguishing it from sibling tools like delete_message or delete_event. However, the phrase '(due fasi)' is ambiguous and not explained, slightly reducing clarity.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical scenarios, or exclusions. Users are left to infer when folder deletion is appropriate.

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