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 destructive and idempotent behavior. The description adds minor context about clearing sensitive data, but does not significantly enhance 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?
Three sentences, each purposeful. No redundancy. Front-loaded with key action.
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 purpose, use cases, and related tools sufficiently.
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%, so the schema fully documents the parameter. The description does not add additional meaning beyond the schema definition.
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 tool deletes a memory by key, using a specific verb and resource. It distinguishes itself from sibling tools like 'remember' and 'recall' by indicating it is the deletion counterpart.
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 guidance on when to use (stale context, task done, clearing sensitive data) and pairs with related tools, offering clear context for tool selection.
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.
Each tool has a highly distinct purpose, from Disney character lookups to financial data and prediction market analysis. Agent can easily distinguish them by name and description.
Naming conventions vary wildly: some use verb_noun (list_characters), others are phrases (ask_pipeworx) or compound nouns (polymarket_arbitrage). No consistent pattern across tools.
34 tools is far too many for a Disney-themed server. Only 3 tools (list_characters, search_characters, get_character) relate to Disney; the rest are general-purpose data tools that belong elsewhere.
For a Disney server, the tool surface is severely incomplete. Missing basic CRUD for characters, no info on movies, parks, or media. Extraneous tools do not fill these gaps.