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 mark destructiveHint and idempotentHint; description reinforces destructive nature and adds context about clearing sensitive data. No contradiction, and the description adds modest behavioral context 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, front-loaded with the verb and resource. Every word earns its place, with no filler or redundancy.
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 deletion tool with one required parameter and clear annotations, the description covers purpose, usage scenarios, and tool relationships. No critical information is missing.
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?
Input schema already documents 'key' with 100% coverage ('Memory key to delete'). Description only reuses 'by key', providing no additional semantics, so baseline 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?
Description clearly states the action (delete) and resource (previously stored memory by key), and distinguishes from siblings by explicitly referencing remember and recall as counterparts.
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 usage scenarios (stale context, task complete, clearing sensitive data) and suggests pairing with remember/recall, giving clear guidance on when to use this tool versus 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.
Most tools have distinct purposes, but the ask/research family is crowded: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route to the same underlying catalog and require careful description reading to select correctly. Prediction-market tools also overlap in scope, though each has a reasonably distinct angle.
All names are snake_case and mostly readable, but conventions are mixed: some are verb_noun (query_layer, resolve_entity), some are noun_noun (entity_profile, pipeworx_feedback, polymarket_arbitrage), and some are adjective_noun or brand-prefixed phrases. No consistent verb/noun ordering pattern exists across the set.
34 tools is too many for the apparent focus, especially since the server is named 'Arcgis Phoenix' but only 3 of the tools are actually GIS tools. The bulk is a sprawling Pipeworx data/prediction-market ecosystem plus unrelated utilities, making the set feel over-stuffed and unfocused.
The Pipeworx data side is fairly complete for lookups, entity profiles, comparisons, validation, and subscriptions, but the ArcGIS Phoenix portion is only search/schema/query and lacks any analysis, geocoding, or editing capability. The presence of generate_llms_txt and scan_dependency highlights that the overall domain is undefined and therefore hard to call complete.