seerr_delete_overriderule

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

The description redundantly repeats 'DESTRUCTIVE: this deletes data', which is already captured by the annotation destructiveHint=true. It adds no context beyond the annotation, such as whether the deletion cascades, requires permissions, or is irreversible.

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 core action is front-loaded in a single compact sentence. However, the trailing 'DESTRUCTIVE: this deletes data' is redundant with the annotation and adds no unique value, slightly reducing efficiency.

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 single-ID delete operation, the description provides the essential action. The presence of an output schema covers return values, but the lack of mention of side effects or permanent consequences is a gap given the destructive nature, despite the annotation.

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 schema description coverage at 0%, the description must clarify the parameter. It only says 'by ID', which is already evident from the parameter name rule_id. It does not explain where to find the ID, its format, or any constraints.

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 'Delete override rule by ID', specifying both the verb (delete) and the resource (override rule). This distinguishes it from sibling tools like seerr_list_overriderule or seerr_update_overriderule.

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 tool name and verb imply when to use it (when an override rule must be removed), but there is no explicit guidance about prerequisites, such as needing to list rules first or warnings about irreversibility. No alternatives are mentioned.

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