pmg_ruledb_rule_delete

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

With no annotations, the description fully discloses the irreversible mutation, dry-run default, and effect on group bindings. The 'MUTATION (MEDIUM)' label and explicit details about execution and raw API response add high transparency.

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 with three sentences, front-loading the purpose and key behavior. Every sentence provides essential information without fluff.

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 the tool's complexity (irreversible mutation, dry-run pattern, multiple sibling tools), the description covers safety, prerequisites, and output behavior. It could mention the dry-run output format, but the existence of an output schema partially mitigates this.

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 context by explaining the dry-run behavior for the confirm parameter and the relationship between id_ and the rule. This goes beyond the schema without redundancy.

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 explicitly states 'delete a PMG RuleDB rule' with a specific verb and resource. It distinguishes from sibling rule tools (e.g., pmg_ruledb_rule_create, pmg_ruledb_rule_get) by focusing on deletion and the irreversible nature.

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 advises to 'List rules first with pmg_ruledb_rules_list', provides dry-run behavior, and explains the confirm flag. However, it does not explicitly mention when not to use this tool versus alternatives like update or attaching actions.

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