delete_chaos_rulePermanently remove a chaos rule by its numeric ID. Use it to clean up proxy test rules when they are no longer needed.
Permanently delete a chaos rule by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The word 'Permanently' reinforces the destructive nature but adds little beyond the annotations, and nothing is said about error behavior for missing ids or downstream effects on captured sessions.
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?
One short sentence, front-loaded with the verb and the irreversibility qualifier. Zero waste.
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 destructive single-param tool, the description plus annotations cover the essentials of what it does and that it is dangerous. However, no output schema and no mention of return value or failure modes, and no pointer to list_chaos_rules to find the id, leaves gaps.
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 description coverage is 0% with a single required numeric id parameter. The description notes the lookup is 'by id', which is the only semantic hint available, but gives no format, source, or how to obtain the id. Baseline for a bare required param with no schema docs.
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?
States a specific verb (delete) and resource (chaos rule) with the key qualifier 'permanently' and the lookup key 'by id'. It does not name sibling tools like toggle_chaos_rule or delete_rule_pack to distinguish the resource class, so it falls short of 5.
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?
No guidance on when to use this versus reversible alternatives like toggle_chaos_rule, which merely disables a rule. An agent has no signal that deletion is irreversible and disable might be preferable. Only implied usage from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.