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 description doesn't need to restate danger. It adds context by explaining what is deleted ('memory by key') and a use case ('clear sensitive data'), going slightly beyond the annotations without contradicting them.
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 concise sentences, each adding value: purpose, usage triggers, and companion tools. Information is front-loaded and no filler exists.
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 single-parameter tool with full schema coverage and clear annotations, this description fully covers purpose, usage, and behavioral expectations. No output schema exists, but none is needed for a simple delete operation.
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 ('Memory key to delete'), so the schema carries the parameter meaning. The description only adds 'by key' which doesn't materially enhance the schema's explanation.
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 uses a specific verb ('Delete') and clearly identifies the resource ('previously stored memory by key'). It distinguishes itself from sibling tools 'remember' and 'recall' by explicitly covering deletion, not storage or retrieval.
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?
Provides explicit when-to-use conditions ('context is stale, task is done, clear sensitive data') and names companion tools ('Pair with remember and recall'), making the intended usage clear and differentiating from 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.
The tools span vastly different domains (AI visibility, data querying, prediction markets, GIS) with clear descriptions individually, but the set lacks a coherent focus. An agent looking for ArcGIS functionality would be distracted by many unrelated tools, causing confusion in tool selection.
Most tool names use snake_case, but there is no consistent verb_noun pattern. Some names are verbs (remember, forget), others are noun phrases (entity_profile, layer_info), and some include underscores inconsistently (generate_llms_txt vs. bet_research). The naming feels arbitrary.
With 33 tools, the count is high, but the vast majority are from Pipeworx and unrelated to the server's stated purpose (Arcgis Roanoke). Only 3-4 tools actually relate to GIS. The tool count is extremely inappropriate for the server's focus.
For the implied domain of ArcGIS Roanoke, the tool surface is severely incomplete, lacking CRUD for map layers, spatial queries, or data management. Conversely, the Pipeworx subset is also incomplete on its own (e.g., missing many data sources). The overall surface fails to serve any single domain well.