create-newsletter-smart-mailboxes

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

Without annotations, the description carries full burden. It discloses default dry run behavior, edits to Apple Mail plist (with backup/atomic preservation), potential creation of many smart mailboxes, scanning of ~400 messages, and performance impact on large mailboxes. Safety advice to review dry run first is included.

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 concise and well-structured with clear sections (Use when, Returns, Do not use when, Safety). Every sentence adds necessary information without redundancy.

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?

Given tool complexity and no annotations, the description covers usage, safety, performance, return values (with output schema present), and behavioral traits. It provides all necessary context for safe and effective use.

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 100%, baseline 3. The description adds value by explaining how parameters work together (e.g., dryRun controls creation vs. proposal) and providing context beyond schema descriptions (e.g., scanning range). While not per-parameter, it enhances overall understanding.

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 tool's purpose: auto-discovering newsletter/bulk senders in INBOXes and optionally creating smart mailboxes per sender. It distinguishes from sibling tools 'create-smart-mailbox' and 'create-mailbox' by specifying when to use each.

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 explicitly provides 'Use when' and 'Do not use when' conditions, including alternative tools (create-smart-mailbox for known senders, create-mailbox for real folders). This gives clear guidance on tool selection.

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