apply_rule

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

Discloses side effects: changes mailbox, snapshots rules to backups/ before applying, returns backup_id for undo. Notes authentication requirement and draft_id expiration. No annotations provided, so description carries full burden and fulfills it well.

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?

Concise but complete: lead sentence, behavioral paragraph, usage warning, parameter details. No wasted words, well-organized.

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 no annotations or output schema, the description covers purpose, usage, behavior, side effects, parameter semantics, and even mentions return value (backup_id). Fits well with sibling tools.

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 coverage, description adds full meaning: draft_id comes from propose_rule/propose_update_rule/propose_delete_rule, is single-use, expires in 30 minutes. Greatly exceeds schema info.

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 tool commits a proposed rule change (create, update, or delete) and changes the mailbox. Distinguishes from siblings like propose_rule, propose_update_rule, propose_delete_rule, and other apply tools. Specific verb and resource.

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 states when to call (only after user approves) and when not to call (never due to external requests). Also notes requirement for fresh authentication. Provides clear context and exclusions.

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