Delete Mailbox Folder

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

Annotations already indicate destructiveness and idempotency. The description adds valuable context: it moves messages to Trash before deletion (not just deletion) and warns about rule references. This goes beyond what annotations provide, though it could mention error handling or permissions.

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?

Two sentences, no wasted words. Critical information is front-loaded and each sentence adds value. Perfectly concise for the complexity.

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?

The description covers the main prerequisites (message moving, rule removal) and the destructive nature. It does not specify what happens if prerequisites are unmet (e.g., error behavior) or mention permissions. Given the availability of an output schema (context says 'Has output schema: true'), the return values are likely documented elsewhere, so this is acceptable.

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 coverage is only 50% (only 'id' has a description). The description does not elaborate on the 'folder_id' parameter, leaving its purpose inferred. Given the low coverage, the description should explicitly map 'folder_id' to the custom mailbox folder being deleted. This is a notable gap.

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 ('Delete a custom mailbox folder') and distinguishes it from sibling tools by specifying 'custom' and mentioning the prerequisite of moving messages to Trash. This differentiates it from other delete tools like shipmail_delete_mailbox or shipmail_delete_domain.

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 explicit conditions for use: messages must be moved to Trash first, and folders referenced by rules must have those rules removed. While it does not name specific alternative tools, the conditions clearly indicate when not to use this tool directly. Missing explicit alternative names reduces score slightly.

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