Delete Rule

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

The description adds 'This action is irreversible' which reinforces the destructiveHint annotation (true). Without the annotation, this would be critical; but since the annotation already signals destructive behavior, the description provides marginal extra value. No contradictions, but no further behavioral details (e.g., cascading effects, permissions) are given.

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 extremely concise with only two sentences, no filler. It is front-loaded with the primary action and immediately follows with a critical caveat (irreversibility). Every word serves a purpose.

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 one-parameter destructive tool with annotations and an output schema, the description provides adequate information. It covers the core action and consequence. While additional details about dependencies or return values could enhance completeness, they are not strictly necessary given the output schema's existence.

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 has 100% description coverage for the single parameter (rule_id described as 'Rule ID.'). The description does not add any additional semantic nuance beyond what the schema provides. Baseline 3 is appropriate given high schema coverage.

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 a rule' which is a specific verb-resource combination. The mention of irreversibility adds important context. It effectively distinguishes from sibling tools like create_rule, update_rule, get_rule, and other delete tools targeting different entities.

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 does not explicitly provide when to use this tool versus alternatives like delete_resource or delete_manufacturing_resource. However, the tool name and title imply it is for rules, and the sibling list confirms distinct entity types. No exclusions or prerequisites are mentioned, but the context is clear enough for an agent to infer when to use it.

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