delete-smart-mailbox

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

With no annotations, the description carries the full burden. It discloses the destructive nature, specifics about modifying SyncedSmartMailboxes.plist, backing up .bak, atomic writes, preserving other smart mailboxes, and non-reversibility in-app. It also advises confirmation and quitting Mail, adding practical operational context.

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 well-structured with labels (Use when, Returns, Do not use when, Safety) and packs substantial guidance into a compact format under 80 words. Every sentence serves a purpose with no filler.

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 single-parameter destructive tool with an output schema, the description covers use case, return confirmation, safety mechanism, preconditions, and alternatives. It is self-sufficient for an agent to invoke correctly without additional context.

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 has no parameter descriptions (0% coverage), so the description compensates by clarifying the 'name' parameter is the smart mailbox name and instructing to use the exact name. This adds practical semantics beyond the raw schema field.

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 opens with 'Use when: deleting an Apple Mail smart mailbox (virtual view) by name,' which is a specific verb+resource statement. It also distinguishes from siblings by explicitly directing to delete-mailbox for real folders and delete-message/batch-delete-messages for messages.

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?

It explicitly states when to use ('deleting an Apple Mail smart mailbox') and when not to use, naming alternatives such as delete-mailbox and delete-message/batch-delete-messages. It also provides actionable preconditions: confirm the exact name with list-smart-mailboxes first and quit Mail first for reliable results.

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