delete-mail-rule

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

Annotations confirm destructiveHint=true, and the description adds 'Deletes a message rule permanently,' reinforcing the behavior. No other behavioral traits are disclosed, but the description aligns with annotations and adds value by emphasizing permanence.

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 sentences with no wasted words: the first state the action, the second provides a helpful tip. Front-loaded and efficient.

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?

For a straightforward delete operation with annotations and full schema, the description is sufficient. It explains the action, permanence, and a useful tip. No output schema exists, but that is typical for deletions.

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%, so parameters are well-documented. The description adds a tip about using the Inbox folder ID, providing extra context for the mailFolderId parameter beyond the schema.

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 'Delete the specified messageRule object.' Verb (delete) and resource (messageRule) are specific, distinguishing it from other delete tools like delete-mail-folder or delete-mail-message.

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?

Provides a tip about using the Inbox folder ID for inbox rules, which is helpful but does not explicitly state when to use this tool versus alternatives or when not to use it. No mention of prerequisites or exclusion criteria.

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