Delete a knowledge item by UUID to remove outdated or incorrect entries from Muninn's shared code index.
Delete a knowledge item by its UUID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | UUID of the knowledge item to delete. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. Beyond the destructive verb it says nothing about irreversibility, required permissions, cascade effects on related items, or behavior when the UUID is unknown.
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 action and resource, containing no filler. Size is proportionate to a single-parameter tool.
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, unannotated mutation with no output schema, the description is too thin: it omits reversibility, error handling for missing UUIDs, and permission requirements that an agent needs before invoking it.
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 single parameter is fully documented in the schema, so the schema does the heavy lifting. The phrase 'by its UUID' only echoes the schema's format hint without adding new meaning.
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 'Delete' plus resource 'knowledge item' with a clear identifier qualifier ('by its UUID'). It is distinguishable from the sibling search_/list_/record_ tools, though it never explicitly contrasts itself with record_knowledge or names a boundary condition.
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 statement of when to use this tool versus record_knowledge, list_knowledge, or the search variants, and no preconditions or consequences of use. The agent must infer that deletion follows a lookup step.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
This server cannot be deployed