delete-rule

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

The description states the destructive nature (rule removed permanently) and safety requirement (explicit user confirmation). It also notes the return value is a confirmation. No annotations are present, so the description carries full burden and does so thoroughly.

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 (4 sentences), front-loaded with use/when-not, returns, and safety. Every sentence adds value without redundancy.

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 a single-parameter tool with an output schema (implied), the description covers purpose, usage guidelines, safety, and return format. It is complete for an agent to invoke correctly.

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 description coverage, the parameter 'name' is only defined by type and minLength. The description adds context by stating 'by name' and instructing to use list-rules to get the exact name, adding practical guidance 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?

The description clearly states the tool's purpose: permanently removing a Mail rule by name. It uses specific verbs and resources, and distinguishes from siblings like disable-rule and create-rule.

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?

Explicit when to use (permanently removing a rule) and when not to use (pausing or creating a rule), with alternative sibling tools mentioned. Also provides a prerequisite: use list-rules first to confirm the exact name.

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