delete-mail-rule

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

Annotations already indicate destructiveHint=true, and the description adds that deletion is permanent, aligning with annotations. However, it does not disclose additional behavioral traits like side effects, prerequisites, or error handling beyond the tip.

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 very concise, consisting of two short sentences with a helpful tip emoji. Every sentence earns its place without unnecessary detail.

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 the destructive nature (annotations), the description is sufficient for a delete operation. It explains permanence and provides a practical tip. Could mention that deletion is irreversible, but 'permanently' covers that. No output schema needed.

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 100% schema coverage, baseline is 3. The description adds value by guiding use of the Inbox folder ID for the mailFolderId parameter, which provides context beyond the schema's simple 'Path parameter' 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?

The description clearly states the tool deletes a specified messageRule object, using the verb 'Delete' and resource 'messageRule object'. This distinguishes it from siblings like create-mail-rule, update-mail-rule, and list-mail-rules.

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 hints at when to use this tool (to delete a mail rule) and provides a tip to use the Inbox folder ID from list-mail-folders for inbox rules. However, it does not explicitly state when not to use alternatives or compare with other delete tools.

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