delete_folder

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

With no annotations, the description carries the full burden. It discloses that the action is irreversible ('Irreversível') and that it deletes all messages in the folder, which is critical behavioral information. However, it does not specify whether subfolders are affected or any permission requirements.

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 concise at two sentences, with the core action stated first and the warning second. It avoids unnecessary elaboration and is well-structured for quick parsing.

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 simple tool with one parameter and no output schema, the description covers the essential behavior and warns about irreversibility. It lacks details on edge cases or error conditions, but given the tool's simplicity, it is reasonably complete. However, it could benefit from clarifying the name parameter's expected format.

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 schema defines a single 'name' string parameter, but the description does not clarify its meaning (e.g., whether it expects a folder name or path). With 0% schema coverage, the description fails to add any semantic value beyond the schema's field name.

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 removes a folder and all messages in it, using the specific verb 'Remove' and resource 'pasta'. It distinguishes from delete_email by specifying the folder context, leaving no ambiguity about what is deleted.

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 provides no guidance on when to use this tool versus alternatives like rename_folder or delete_email. It does not mention any conditions or exclusions, leaving the agent to infer usage from the name alone.

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