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 agent knows it's safe to delete and idempotent. The description adds context ('clear sensitive data') implying irreversibility, but does not describe behavior for missing keys. Overall adequate for a simple delete tool.
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 concise: two sentences, no wasted words. First sentence states the action, second provides usage guidance. Front-loaded and 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?
The tool is simple (one parameter, no output schema) and annotations cover safety. The description fully explains what it does, when to use it, and how it relates to siblings. No gaps remain for this use case.
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 a clear description for the single parameter 'key: Memory key to delete'. The description does not add extra meaning beyond what the schema provides, so baseline score of 3 applies.
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.' It specifies the verb (delete) and resource (memory), and distinguishes itself from sibling tools like 'remember' and 'recall' by focusing on deletion.
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 explicitly states when to use the tool: 'when context is stale, the task is done, or you want to clear sensitive data.' It also suggests pairing with 'remember' and 'recall', providing clear guidance on usage context.
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.
Several tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded serve nearly the same routing purpose, with the beta variant currently identical to the stable one, and deep_research also overlaps for broad research. However, most other tools have clearly distinct functions, and descriptions provide usage guidance, so ambiguity is moderate.
Most names are snake_case and readable, but patterns vary between verb_noun (compare_entities, resolve_entity), noun phrases (entity_profile, polymarket_edges), and bare verbs (remember, subscribe). The pipeworx_ and polymarket_ prefixes are used inconsistently across the set, and the server name 'Unicode' does not align with the tool names.
At 34 tools, the server is overloaded for a focused purpose, especially since only three tools relate to Unicode despite the server name. Many Polymarket and Pipeworx tools could be consolidated, and the count exceeds the well-scoped range of 3-15 tools, making the set feel bloated and unfocused.
The server name claims to be about Unicode, but only char_info, escape_string, and unescape_string cover that domain, missing common operations like normalization, case conversion, and encoding validation. For the broader data-access domain the surface is fairly complete, yet there is no tool to fetch a specific pipeworx:// citation URI, leaving cited records unfetchable within the tool set—an obvious gap relative to the stated capabilities.