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 already declare destructiveHint=true and idempotentHint=true, so the description adds context about what gets deleted (stale context, task done, sensitive data) and that it acts on 'previously stored memory'. No contradictions.
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 sentences with no wasted words. Front-loaded with the action and resource, followed by usage guidelines and pairing recommendation. Highly efficient.
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 tool with one parameter and no output schema, the description fully covers what the tool does, when to use it, and how it relates to siblings. No gaps.
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 only parameter 'key' is described in the schema. The description does not add additional meaning beyond the 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?
The description clearly states 'Delete a previously stored memory by key', specifying the verb (delete) and resource (previously stored memory). It distinguishes from siblings 'remember' and 'recall' by its action (deletion vs. storage or retrieval).
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 describes when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. Also recommends pairing with 'remember' and 'recall', providing clear context for its use relative to 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, such as ask_pipeworx, ask_pipeworx_grounded, entity_profile, compare_entities, and validate_claim, all retrieving entity data. Agents may struggle to choose correctly between them. Likewise, bet_research, polymarket_edges, and polymarket_arbitrage cover similar prediction market territory.
All tool names use underscores, but the verb/noun order varies: compare_entities (verb_noun), entity_profile (noun_noun), scan_competitor_ai_presence (verb_noun), bet_research (noun_verb). Some names are overly long (scan_competitor_ai_presence). The pattern is readable but not fully consistent.
With 31 tools, the count is high but not extreme. However, the set covers geospatial, data retrieval, prediction markets, npm scanning, and memory/feedback - too broad for a single server. Many tools feel added without clear justification, making the set feel bloated.
The geospatial subset is incomplete (missing elevation, distance matrix, isochrones). The data access tools overlap rather than form a complete API surface (e.g., no entity update/delete). Prediction market tools are numerous but redundant. The server tries to do too much and lacks depth in any area.