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 provide destructiveHint=true and idempotentHint=true. The description reinforces the destructive nature and adds usage context (clearing sensitive data), adding value beyond 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?
Two concise sentences with front-loaded purpose, zero wasted words. Every sentence adds value.
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?
Given a simple tool with one parameter, no output schema, and good annotations, the description adequately covers purpose, usage, and pairing. It lacks mention of behavior on missing key but is complete enough for typical use.
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 parameter 'key', with a clear description. The tool description adds no additional parameter information beyond what the schema provides, 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 'Delete a previously stored memory by key' uses a specific verb (delete) and resource (memory by key), clearly distinguishing the tool from siblings like 'remember' and 'recall'.
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' and directs pairing with 'remember' and 'recall' as 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.
Several tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research all answer questions; entity_profile, compare_entities, recent_changes all cover company data). Descriptions provide distinctions, but an agent can easily misselect, especially between the Pipeworx query tools.
Tool names follow mixed conventions: some use verb_noun (list_subscriptions, unsubscribe), others use descriptive phrases (ai_visibility_check, polymarket_arbitrage) or nouns (deep_research, entity_profile). No consistent pattern, making it harder to predict tool names.
With 32 tools covering diverse domains (data lookups, prediction markets, memory, subscriptions), the server feels overloaded. The scope would be better served by splitting into smaller, focused servers (e.g., data query, prediction market, memory). Many tools are peripheral to a core purpose.
The tool surface is fairly comprehensive within its domains: CRUD for memory (remember/recall/forget), subscription management, extensive data query options, and prediction market analysis. Minor gaps exist (no update memory, no direct trading), but agents can work around them.