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?
The annotations already provide destructiveHint=true and idempotentHint=true, so the description's 'delete' action is consistent. It adds value by specifying use cases (stale context, done tasks, sensitive data) and the relationship with remember/recall, which goes beyond the annotations.
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 two sentences, front-loaded with the core action followed by usage context. Every sentence earns its place with no redundancy or irrelevant information.
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 delete tool with strong annotations and a clear schema, the description is fully complete. It covers the operation, when to use it, and how it relates to sibling tools, leaving no significant 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?
The schema provides full coverage of the single 'key' parameter with a clear description ('Memory key to delete'). The tool description does not add additional parameter details, so a baseline score of 3 is appropriate given high schema coverage.
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 tool deletes a previously stored memory by key, using the specific verb 'Delete' and resource 'memory'. It distinguishes itself from siblings like remember and recall by focusing on the deletion operation.
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 lists scenarios for use: when context is stale, task is done, or clearing sensitive data. It also mentions pairing with remember and recall, providing context. However, it lacks explicit when-not-to-use guidance, so it doesn't fully meet the 5-point criterion.
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 overlap heavily: ask_pipeworx, ask_pipeworx_beta (currently identical), and ask_pipeworx_grounded share the same routing core, while bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_fill_risk all target prediction-market edge detection. The descriptions are detailed, but an agent must read a lot of nuance to avoid selecting the wrong tool.
All names are lowercase snake_case and readable, but the convention is mixed: verb_noun names like encode_html and resolve_entity sit alongside bare verbs like remember and forget, and noun-phrase names like entity_profile, recent_changes, and polymarket_fill_risk. The ask_pipeworx_* and polymarket_* families are internally consistent, but there is no single predictable pattern across the whole set.
At 33 tools this exceeds the 25+ threshold for a heavy set. The bloat is especially noticeable because the server is named Htmlentities yet only encode_html and decode_html relate to that purpose; the rest are unrelated Pipeworx research, prediction-market, memory, and subscription utilities.
The Pipeworx surface is broadly complete: ask/grounded/deep_research/discover/suggest cover data access, entity_profile/compare_entities/recent_changes/validate_claim cover entity workflows, and subscriptions and memory have create/list/delete lifecycles. Minor gaps such as no update operation for subscriptions or memories are workable, and encode/decode fully covers the literal Htmlentities purpose.