Remove a fact by UUID and delete all of its linked sources. Use when a stored fact is outdated or incorrect and must be cleared from the knowledge base.
Delete a fact and its sources.
Args: fact_id: Fact UUID string
Returns: Success status
| Name | Required | Description | Default |
|---|---|---|---|
| fact_id | Yes |
Changes observed during successful MCP inspections.
v1.1.0v1.0.46v1.0.42Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description discloses that deletion also removes associated sources, which is important behavioral information. However, it omits details about irreversibility, potential side effects, or any permission requirements, leaving gaps for the agent.
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 extremely concise and front-loaded, with no filler. The essential purpose and parameter are stated immediately, and it remains under a few sentences without unnecessary detail.
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 simple single-parameter delete operation, the description is mostly sufficient: it identifies the action, input, and output. However, it lacks context on irreversibility, success/error semantics, and any cascading behaviors beyond sources, leaving some ambiguity for the agent.
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%, so the description must compensate. It adds that fact_id is a UUID string, which clarifies the format beyond the schema's plain string type. Yet it does not elaborate on how the ID is used or any constraints, so only minimal added value.
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 clearly states the verb 'delete' and the resource 'a fact and its sources', making it distinct from siblings like add_fact and update_fact. It unambiguously conveys the operation's scope.
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 provides no guidance on when to use this tool versus alternatives such as update_fact, nor any conditions under which deletion is appropriate. It simply states the action without context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.