delete_rule

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context beyond these hints, notably that deleting the rule does not move emails. This helps set expectations about the operation's side effects. However, it does not mention irreversibility or permission requirements, which is partly covered by the destructive hint.

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 front-loaded with the main purpose. It uses a single informative sentence about behavior plus a short parameter section. No unnecessary words or repetition—every part 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?

For a simple rule-deletion tool with one parameter, the description covers the key aspects: what it does, its effect (or lack thereof) on emails, and the parameter format. The presence of an output schema and annotations fills other gaps. A minor omission is explicit mention of permanence, but destructiveHint already conveys that. Overall, the description is sufficiently complete.

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?

The input schema only defines the 'rule' field as a string with no explanation. The description compensates fully by specifying that it can be either a rule name (as shown in list_rules) or a raw rule ID. This is essential guidance for correct usage, and the description provides it clearly.

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 function: deleting an auto-sorting rule. It uses a specific verb ('delete') and resource ('rule'), distinguishing it from sibling tools like create_rule and list_rules. The additional note 'Emails do not move' clarifies the tool's scope.

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 implies usage for deleting rules but does not explicitly state when to use it over alternatives or provide exclusions. It gives helpful guidance on the 'rule' parameter format (name from list_rules or raw ID), but lacks explicit contextual direction. This is acceptable but not outstanding.

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