delete_decisionPermanently remove a decision session by its decision ID; export the session first if you need to keep its data for later reference.
Permanently delete a decision session. Consider export_decision first.
| Name | Required | Description | Default |
|---|---|---|---|
| decision_id | Yes | Id returned by start_decision, e.g. 'dec-a3f2'. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds the crucial irreversibility note ('Permanently delete') and a pre-step recommendation, which goes beyond the annotations.
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?
Two short, front-loaded sentences. The destructive warning is first, the alternative second. 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?
Given annotations cover safety and an output schema exists, the description is nearly complete for a delete tool. The only missing element is any scope/authorization note, but that is often implied and not critical for invocation.
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 the schema already documents decision_id with an example format. The description adds no parameter detail, but baseline is 4 for a single fully documented required parameter; it could have restated the ID origin but doesn't need to.
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?
Specific verb+resource: 'Permanently delete a decision session.' Distinguishes itself from siblings by naming export_decision as the alternative and the permanent-delete 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?
Explicitly recommends considering export_decision first, giving a clear when-to-use-this-vs-alternative cue. No explicit when-not-to-use beyond that, but the guidance is actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.