delete_rule

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

The description states 'requires user confirmation' and 'cannot be undone,' which adds context beyond annotations. However, there is a contradiction: annotations set idempotentHint=true, but a delete operation that fails on retry (index already deleted) is not truly idempotent. This inconsistency reduces 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?

Two succinct sentences with front-loaded verb and resource. No unnecessary words. Every sentence earns its place.

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, and consequences. For a simple tool with one parameter and an output schema, this is sufficiently complete. Minor absence of error behavior (out-of-bounds index) 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 100%, providing baseline of 3. The description adds meaning by specifying that the index is '1-based positional index from list_rules,' which clarifies origin and usage beyond the schema description.

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?

Clearly states the action (delete) and resource (Mail.app rule) and specifies the indexing method (1-based positional index). Differentiates from siblings like delete_mailbox and delete_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 mentions requirement for user confirmation and irreversibility, providing clear usage context. Does not explicitly list when not to use or alternatives, but the nature of a delete operation makes this less critical.

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