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 indicate destructiveHint=true; the description adds that it 'clears sensitive data', reinforcing the destructive nature. No contradictions. Could mention idempotent behavior but not required.
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: first defines the action, second provides usage guidance. No fluff; every sentence earns its place.
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 the tool's simplicity (single parameter, no output schema), the description covers all necessary information: action, usage context, and related tools.
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 describes the 'key' parameter sufficiently. The description does not add additional semantic information 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?
Clearly states 'Delete a previously stored memory by key', with a specific verb and resource. Distinguishes from sibling tools 'remember' and 'recall' by indicating 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?
Explicitly states when to use: when context is stale, task done, or to clear sensitive data. Also suggests pairing with 'remember' and 'recall', providing clear context for usage.
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 roles, and the extensive descriptions help differentiate intent, but the ask_pipeworx family—especially ask_pipeworx_beta, which is currently identical to ask_pipeworx—creates real ambiguity. Overlapping entry points like ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim could also cause misselection without careful reading.
All 34 tools use consistent snake_case, and clear verb-led or noun-prefixed patterns emerge across families like ask_pipeworx*, polymarket_*, and remember/recall/forget. Minor deviations such as ai_visibility_check and recent_changes being noun phrases rather than verb_noun constructions prevent a perfect score.
34 tools is well above the 25-tool threshold for over-scoping, making the set heavy for an agent to navigate. While the server spans many domains, several tools like generate_llms_txt, scan_dependency, and ai_visibility_check feel tangential to the core news/research purpose and would be better split into separate servers.
The core news/research domain is well covered: lookup, grounded verification, deep multi-source research, entity profiles, comparisons, subscriptions, and alert feeds are all present with no obvious dead ends. Minor gaps exist—such as no direct full-text article retrieval or a dedicated free-text news search beyond latest_news filters—but agents can work around them.