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; description adds no behavioral details beyond 'Delete', which is consistent. Minimal additional value over 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 sentences with no waste: first sentence states purpose, second gives usage guidance. Front-loaded and efficient.
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 simple tool with one parameter, no output schema, and good annotations, the description covers purpose and usage completely.
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 description coverage is 100% with good documentation for 'key'. Description only restates the parameter's purpose without adding new meaning.
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?
States 'Delete a previously stored memory by key' with a specific verb and resource, and distinguishes from siblings '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?
Explicitly lists when to use (stale context, task done, clear sensitive data) and suggests pairing with remember and recall, providing clear context and 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 clearly distinct purposes, but there is some overlap: ask_pipeworx and ask_pipeworx_grounded are very similar, and the multiple Polymarket tools could be confused. The memory tools (remember, recall, forget) are distinct.
Tool names consistently use snake_case, but the pattern is not strictly verb_noun. Some names are descriptive phrases (e.g., scan_competitor_ai_presence), while others are straightforward (e.g., keyword_overview). Overall readable but not highly consistent.
32 tools is on the high side for a single server, but the scope is broad (SEO, finance, FDA, betting, memory). The tool count feels slightly excessive, yet each tool appears justified by its specific use case.
The tool set covers a wide range of business research needs: SEO, SEC filings, FDA data, betting analytics, and memory. Minor gaps exist (e.g., no direct social media or HR data), but the coverage is impressive for a general-purpose data server.