forgetDelete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Memory key to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide destructiveHint=true; description adds context for why deletion is used (stale data, sensitive data), going beyond the annotation without contradicting it.
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 compact sentences with no wasted words; action and context are front-loaded.
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 one-parameter tool with strong annotations and schema, the description covers all necessary context: purpose, when to use, and relationship to siblings.
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% with clear description of 'key' parameter. Description does not add extra meaning beyond schema, so baseline score of 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?
Description states 'Delete a previously stored memory by key' – a specific verb and resource. It distinguishes from sibling tools like 'remember' and 'recall' by naming them.
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 states when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. Also directs to pair with 'remember' and 'recall', indicating alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have overlapping purposes (e.g., three variants of ask_pipeworx, several polymarket tools, and multiple discovery/entity tools). Despite detailed descriptions, the similiar functionalities create confusion for an agent selecting among them.
Tool names are consistently in snake_case but the verb/noun pattern is mixed: some start with verbs (ask_, list_, remember_), others with nouns (entity_profile, polymarket_edges). This inconsistency reduces predictability.
35 tools is high for a single server, especially when the scope spans two disparate domains (HDX humanitarian data and Pipeworx data platform). Many tools could be logically split into separate, more focused servers.
The tool set covers a wide range of functionality (data retrieval, comparison, monitoring, memory) but has notable gaps: no direct data download tool for HDX resources, no account management, and no exploration of Pipeworx packs beyond discover_tools.