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 adds value by explaining the purpose ('previously stored memory') and the rationale for deletion (stale, done, sensitive data). No contradiction with 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 just two sentences, front-loaded with the primary action, followed by usage guidance. Every word earns its place with no filler.
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 tool with one parameter, no output schema, and clear annotations, the description fully covers purpose, usage, and context. It is complete and actionable.
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 describes 'key' as 'Memory key to delete' with 100% coverage. The description repeats 'by key' but adds no new details about formats, defaults, or edge cases. Baseline 3 applies as schema does the heavy lifting.
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's function with a specific verb ('Delete') and resource ('a previously stored memory by key'), which immediately distinguishes it from sibling tools 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?
Explicit use cases are provided ('context is stale, the task is done, or you want to clear sensitive data'), and the description suggests pairing with 'remember' and 'recall' as related tools. It does not explicitly say when not to use, but the guidance is clear and practical.
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.
Many tools overlap in purpose, particularly the ask_pipeworx variants (stable, beta, grounded) and deep_research, making it difficult for an agent to choose correctly. Additionally, the Arcgis-specific tools are buried under numerous general Pipeworx tools.
Most tools follow a verb_noun pattern (e.g., ask_pipeworx, compare_entities), but there are minor inconsistencies like ai_visibility_check vs scan_competitor_ai_presence and the simpler Arcgis tool names.
With 34 tools, the server is overloaded, especially since the majority are Pipeworx meta-tools unrelated to the Arcgis Lubbock purpose. A well-scoped ArcGIS server would have far fewer tools.
For an ArcGIS server, only three tools directly serve that purpose (search_datasets, layer_info, query_layer), lacking editing, analysis, or visualization capabilities. The remaining tools address a completely different domain.