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 disclose destructiveHint=true and idempotentHint=true. The description adds the 'clear sensitive data' use case but does not explain behavior for missing keys, return values, or whether deletion is permanent beyond what annotations imply.
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?
Three short sentences, front-loaded with the core action. The first sentence states what it does, the second gives use cases, and the third provides sibling context. No wasted words.
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?
This is a simple one-parameter destructive tool. With annotations covering safety and schema covering parameters, the description adds appropriate when-to-use context and sibling relationships. Fully adequate for the tool's complexity.
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% for the single required 'key' parameter, and its description ('Memory key to delete') fully explains its meaning. The tool description only repeats 'by key' and does not add meaningful extra semantics.
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 starts with a specific verb+resource: 'Delete a previously stored memory by key.' This clearly distinguishes the tool from siblings like remember and recall, which store and retrieve memories respectively.
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 ('context is stale, the task is done, or you want to clear sensitive data') and mentions pairing with remember and recall. It lacks an explicit when-not-to-use statement, but the guidance is otherwise clear.
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.
Most tools have clearly distinct purposes, but there is some overlap among the numerous Pipeworx query and prediction market tools (e.g., polymarket_arbitrage vs. polymarket_edges vs. polymarket_fill_risk). Descriptions help differentiate them, so the ambiguity is minor.
Tool names use a mix of verb_noun patterns (e.g., list_subscriptions, validate_claim), phrases (ask_pipeworx, bet_research), and standalone nouns (pipeworx_feedback). While readable, the lack of a single consistent convention makes the set feel less cohesive.
33 tools is on the high side, with many highly specialized prediction market and Pipeworx management tools. The server's name 'emojihub' suggests a narrow focus, but the actual scope is much broader, making the count feel somewhat inflated for its apparent purpose.
The tool set covers a vast domain: factual data retrieval, company profiles, comparisons, claim validation, prediction market analysis, memory, subscriptions, and emoji lookup. Minor gaps exist (e.g., no direct tool for simple web search), but overall coverage is comprehensive.