Permanently remove a decision-memory record by its ID. Review decisions first to confirm, then delete to free up memory and keep records accurate.
Delete one decision-memory record by id. Deletion is permanent; review with list_decisions first. Returns the deletion confirmation for the decision_id.
| Name | Required | Description | Default |
|---|---|---|---|
| decision_id | Yes | Decision ID to delete. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already set destructiveHint=true, but the description adds the crucial detail 'Deletion is permanent' and clarifies that a deletion confirmation is returned for the decision_id. This goes beyond the structured hints without contradicting them.
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 tightly packed sentences with no waste. The action verb is front-loaded, followed by a warning and a return-value note. Every phrase earns its place.
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 single-parameter deletion tool, the description covers the action, the permanence, the prerequisite review step, and the return value. Combined with full schema coverage and accurate annotations, nothing essential is missing.
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% and the parameter is already described as 'Decision ID to delete.' The description adds minimal semantic value, just reiterating the id-based targeting with 'by id.' Baseline 3 is appropriate.
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 the specific verb 'delete' and resource 'decision-memory record' with id-based targeting. This clearly distinguishes it from siblings like list_decisions and get_decision.
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?
Provides a concrete guideline to review with list_decisions before deleting, which implies when this tool is appropriate. It does not explicitly name alternatives or when-not-to-use scenarios, but the permanent-deletion warning effectively discourages careless use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.