delete-smart-mailbox

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the tool is destructive, modifies SyncedSmartMailboxes.plist, creates a backup, writes atomically, preserves other smart mailboxes, and that removal is not undoable in-app. This exceeds expectations for transparency.

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 structured with clear labels (Use when, Returns, Do not use when, Safety), making it easily scannable. Every sentence provides necessary information without redundancy, and the most critical usage guidance appears first.

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?

This destructive tool has no annotations, but the description covers prerequisites, safety, file-level behavior, and exclusions. It also names the confirmation tool and the need to quit Mail, making it complete for safe invocation.

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?

Although schema description coverage is 0%, there is only one parameter ('name') whose meaning is self-evident. The description adds value by emphasizing the name must be exact and recommending list-smart-mailboxes to confirm it, which indirectly clarifies the parameter's expected value.

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 uses a specific verb ('deleting') and resource ('Apple Mail smart mailbox (virtual view) by name'), clearly distinguishing this tool from siblings. It also explicitly names alternatives for real folders and messages, leaving no ambiguity about its 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 provides explicit 'Use when' and 'Do not use when' guidance, naming alternative tools (delete-mailbox, delete-message, batch-delete-messages). It also instructs to confirm the exact name with list-smart-mailboxes and quit Mail first, giving concrete prerequisites.

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