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 only states that the tool deletes a folder/mailbox, but it does not mention whether the deletion is permanent, whether the folder must be empty, whether its contents are also removed, or whether any confirmation or special permissions are required.

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, concise sentence that front-loads the action and target resource. Every word contributes meaning, and there is no redundant or filler content.

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 one-parameter delete operation, the description plus schema is minimally viable. However, because it is a destructive action with no annotations or output schema, it would benefit from stating deletion consequences such as irreversibility or cascading removal of contained emails.

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 already fully describes the only parameter: 'Folder name to delete', so schema coverage is 100%. The description adds no parameter-specific meaning beyond what the schema provides, which is acceptable under the baseline for high schema coverage.

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 states a specific verb ('Delete') and a specific resource ('folder/mailbox from the one.com mail account'), making it easy for an agent to distinguish this from sibling tools like delete_emails, create_folder, and rename_folder. It clearly identifies the operation and scope.

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 when to use the tool: when a folder or mailbox in the one.com mail account needs to be deleted. However, it provides no explicit context about when not to use it, such as preferring delete_emails for deleting individual messages rather than a whole folder.

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