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. The description adds context about clearing data and sensitive data but does not detail side effects (e.g., permanence, error behavior). Since annotations cover the core behavioral traits, the description adds moderate value.
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 three sentences: purpose, usage guidelines, and sibling reference. Every sentence is valuable, no wasted words, and the most critical information is front-loaded.
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 a single parameter, existing annotations, and no output schema, the description covers purpose, usage, and tool relationships. It does not mention error behavior for missing keys, but overall it is sufficient for a simple destructive 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 the parameter 'key' described as 'Memory key to delete'. The tool description does not add further parameter semantics beyond the schema. With high schema coverage, baseline is 3.
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 explicitly states 'Delete a previously stored memory by key', clearly identifying the verb (delete) and resource (memory by key). It distinguishes from sibling tools like 'remember' and 'recall' by specifying the deletion action and referencing their pairing.
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?
The description provides explicit usage scenarios: 'Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also suggests pairing with siblings. However, it does not explicitly state when NOT to use or provide exclusions.
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.
Tools are generally distinct but several clusters (ask_pipeworx family, polymarket family) have highly similar names that could cause confusion. For example, ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all appear to do similar things with subtle differences. The agent would need to read descriptions carefully to pick the right one.
Most tools follow a verb_noun pattern (e.g., compare_entities, resolve_entity, validate_claim). However, a few are single verbs (remember, recall, forget) or have inconsistent suffixes (ask_pipeworx_beta, walkscore_score). This is mostly consistent but not perfectly uniform.
32 tools is quite high, bordering on excessive. While each tool serves a distinct purpose, the sheer number may overwhelm the agent. However, the tools cover a wide range of functionality, so the count is not unreasonable for a comprehensive data platform.
The tool set is comprehensive for querying data, conducting research, managing subscriptions, and evaluating bets. It includes meta-tools for discovery and memory. Notable gaps include user account management and direct file handling, but overall coverage is strong.