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 provide destructiveHint=true and idempotentHint=true. Description adds context about clearing sensitive data, but no additional behavioral details beyond deletion. Slight value added.
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 action, then usage guidance. No redundancy.
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?
Simple tool with one parameter and no output schema. Description, annotations, and schema provide complete guidance for correct invocation.
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 'Memory key to delete' description. The tool description does not add further meaning beyond the schema, so baseline 3 is appropriate.
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 uses specific verb 'delete' and resource 'memory by key', clearly defining the tool's function. It distinguishes from siblings by referencing 'remember' and 'recall' as complementary tools.
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 states when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. Also names related tools for pairing.
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.
While most tools have detailed descriptions, the large number of similar data-querying tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, bet_research, etc.) and overlapping domains (Polymarket, company research, medical) create ambiguity for an agent.
Tool names mix conventions: snake_case (ai_visibility_check, ask_pipeworx), camelCase absent, some with 'pipeworx' prefix, others not (bet_research, compare_entities). No consistent verb_noun pattern.
33 tools for a server named 'Medical Codes' is excessive and misaligned. The vast majority of tools cover unrelated domains (finance, prediction markets, general research), making the count inappropriate for the stated purpose.
For medical coding, only three tools exist (search_icd10, search_loinc, search_medical_terms). The rest are tangential or unrelated, leaving severe gaps in medical code coverage.