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 and idempotentHint, so the description doesn't need to repeat those. It adds minimal behavioral context beyond stating the delete action and mentioning 'sensitive data,' but does not disclose additional traits like permissions or edge cases. The bar is lower with annotations, yet the added value is limited.
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, front-loaded with the core action. The first sentence is immediately informative, and the second adds usage context without verbosity. Every word earns its place.
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, existing annotations, and no output schema, the description covers the essential purpose, usage, and relationship to siblings. It is sufficient for an agent to select and invoke the tool correctly.
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?
The input schema fully describes the single 'key' parameter with 100% coverage. The description only repeats 'by key' without adding format, constraints, or examples beyond what the schema already provides, so it meets the baseline but adds no extra value.
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 clearly states the tool's action with a specific verb and resource: 'Delete a previously stored memory by key.' It distinguishes itself from sibling tools like remember and recall by focusing on deletion of existing memories.
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 provides when to use the tool: 'Use when context is stale, the task is done, or you want to clear sensitive data.' It also references alternatives by pairing with remember and recall, giving the agent clear guidance on inter-tool relationships.
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.
The tool set is dominated by a huge number of unrelated tools for data lookup (Pipeworx, Polymarket, etc.), with only 4 superhero-specific tools. Many tools serve overlapping purposes (e.g., ask_pipeworx, deep_research, suggest_questions all handle general queries), making it very difficult for an agent to distinguish the right tool.
Naming conventions are highly inconsistent: some tools use CamelCase (ask_pipeworx, discover_tools), others use snake_case (get_hero, list_all, compare_entities), and some use long descriptive phrases (polymarket_arbitrage, scan_competitor_ai_presence). This mixture makes it hard to predict tool names.
With 34 tools, the count is far too large for a server named 'superhero'. Most tools are unrelated to superheroes, making the set seem bloated and misaligned with the server's stated purpose. A focused superhero server would need at most 10 tools.
For the superhero domain, the tool set is severely incomplete: only basic retrieval of heroes and powerstats, with no search, filtering, creation, comparison, or battle mechanisms. For the broader data access domain it is more complete, but that is not the server's name.