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?
The description confirms the destructive nature ('Delete') and adds context about clearing sensitive data, which complements the annotations (destructiveHint=true). However, it does not disclose potential side effects like cascade deletions or reversibility, but annotations already cover the destructiveness, so 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 two sentences with no wasted words. The action is front-loaded, followed by usage guidance and sibling references. Every sentence 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, no output schema, and annotations covering destructiveness, the description is complete. It covers purpose, usage context, and relation to siblings, leaving no critical gaps.
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 schema already describing the 'key' property as 'Memory key to delete'. The description only mentions 'by key', adding no extra meaning beyond the schema. Baseline 3 is appropriate as the description does not need to compensate.
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 deletes a memory by key, using a specific verb and resource. It distinguishes from siblings 'remember' and 'recall' by indicating deletion, and provides concrete usage scenarios (stale context, task done, clear sensitive data).
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 gives explicit when-to-use conditions ('context is stale, the task is done, clear sensitive data') and suggests pairing with related tools, but does not explicitly state when not to use or compare with alternatives beyond implying 'remember' and 'recall' are for storage and retrieval.
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 mostly distinct but there is some overlap among lookup tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile) and among Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage). Agents might occasionally struggle to choose the right one.
Naming is inconsistent: some use verb_noun snake_case (ask_pipeworx, compare_entities), some are single words (forget, recall, remember), and others are noun-based (compliance_catalog, entity_profile). No consistent pattern.
With 34 tools, the count is too high for a server named 'ISO Standards'. The majority of tools are unrelated to ISO standards (e.g., Polymarket, memory, web scraping), making the scope highly inappropriate.
As an ISO standards server, the tool set is severely incomplete. Only 4-5 tools (search_standards, get_standard, compliance_catalog, open_data_files) actually deal with ISO standards. Essential operations like comparing standards or browsing revisions are missing.