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, indicating destruction. Description confirms deletion and adds context about clearing sensitive data. It does not disclose idempotent behavior (already in annotations) or other side effects, but given annotations, 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?
Two sentences: first states action, second provides usage guidance and pairing. No wasted words, front-loaded with purpose.
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 and no output schema, the description covers purpose, usage, and pairing. It could mention idempotent behavior or behavior when key doesn't exist, but not essential.
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% for the single parameter 'key', with schema description 'Memory key to delete'. Description does not add additional meaning beyond what the schema already provides.
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' which identifies the verb and resource. It explicitly pairs with 'remember and recall', distinguishing 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?
Description explicitly lists when to use: when context is stale, task is done, or to clear sensitive data. It mentions pairing with remember and recall, implying alternatives. However, it does not explicitly state when not to use it.
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_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and multiple Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, etc.) could cause confusion for an agent selecting the appropriate tool.
Tool names mix snake_case and camelCase inconsistently, with no strong verb_noun pattern. Examples include 'ask_pipeworx' vs 'discover_tools' vs 'validate_claim', indicating a lack of naming convention.
33 tools is high for a single server, including many utility tools (memory, subscriptions) that seem peripheral to the core regulatory/data domain. This suggests scope creep and could overwhelm agents.
The tool set covers a wide range of regulatory and financial data needs, including company profiles, entity comparison, claim validation, FDA catalysts, and prediction market analysis. Minor gaps exist (e.g., no tool for editing data), but overall it is comprehensive for its stated purpose.