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?
Description confirms destructive nature, aligning with annotations (destructiveHint=true). Adds 'clear sensitive data' context. No contradiction with annotations; idempotentHint=true is consistent.
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 sentences, no wasted words, action verb first, efficient and clear.
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 single parameter and annotations, description adequately covers purpose. No output schema, but response format is not critical. Could mention idempotency or error handling, but not required for this simple tool.
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 parameter 'key' described as 'Memory key to delete'. Description adds no extra meaning beyond the schema, 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 'Delete a previously stored memory by key', specifying the verb (delete) and resource (memory by key). Distinguishes from siblings like remember and recall by focusing on 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 lists use cases: stale context, task completion, clearing sensitive data. Mentions pairing with remember and recall, but doesn't explicitly state when not to use or compare to alternatives beyond siblings.
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 are difficult to distinguish: ask_pipeworx and ask_pipeworx_beta are currently identical, and ask_pipeworx_grounded, deep_research, and ask_pipeworx have fuzzy boundaries. The polymarket_* family plus bet_research also overlap heavily, requiring agents to carefully parse long descriptions to avoid misselection.
Naming is predominantly snake_case with a verb-first pattern (ask_, search, subscribe, unsubscribe, list_) and clear prefix families like polymarket_ and pipeworx_. Minor deviations like ai_visibility_check and entity_profile use noun-first phrasing, but the overall pattern is still predictable and readable.
33 tools is heavy for any single server, and the count is especially inappropriate given the server is named Digitalnz but only two tools (search, record) serve that domain. The rest form an unrelated grab-bag of data research, prediction-market, AI-visibility, memory, and utility tools.
The research workflow is fairly well covered: ask/grounded/deep modes, entity resolution, comparisons, claim validation, subscriptions, and alerts all exist. However, the DigitalNZ surface is nearly absent—just search and record—which is a significant gap for the declared server name, while other domains like AI visibility and npm dependencies are isolated one-offs.