delete-smart-mailbox

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

Declares 'destructive' nature, describes the specific file modified (SyncedSmartMailboxes.plist), mentions backup and atomic write, and states removal is not undoable in-app. This far exceeds the burden given no annotations.

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?

Well-structured: usage statement, return info, exclusions, safety details. Every sentence adds value; no wasted words.

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?

Covers purpose, usage, safety, and return value (confirmation of deletion). For a single-parameter destructive tool, this is complete. Output schema existence further reduces need to describe return 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?

With 0% schema description coverage, the description clarifies the parameter 'name' by stating the action is 'by name' and emphasizes using the exact name. Although no format details are given, for a simple string this is sufficient.

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?

Description clearly states 'deleting an Apple Mail smart mailbox (virtual view) by name'. Distinguishes from siblings by specifying it's for smart mailboxes, not real folders or 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?

Explicitly provides 'Use when:' and 'Do not use when:' sections, naming alternative tools (delete-mailbox, delete-message). Additionally advises confirming the name with list-smart-mailboxes and quitting Mail first.

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