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 and idempotentHint=true, so the description doesn't need to restate those. It adds only the use-case context (cleanup of stale/sensitive data) but no additional behavioral traits like error handling or side effects. With annotations doing the heavy lifting, this is adequate but not exceptional.
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 the primary action first and usage guidance second. Every sentence earns its place with 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?
For a single-parameter destructive operation with robust annotations (destructive, idempotent) and full schema coverage, the description fully covers what the tool does, when to use it, and related tools. No output schema is needed, and no obvious gaps remain.
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%, so the schema already documents the 'key' parameter as 'Memory key to delete'. The description merely restates this ('by key'), adding no extra meaning. Baseline 3 is appropriate given the schema's completeness.
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 ('Delete a previously stored memory by key') with a specific verb and resource. It distinguishes itself from sibling tools by pairing with 'remember and recall', making its role in the memory lifecycle explicit.
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?
Provides explicit usage conditions ('Use when context is stale, the task is done, or you want to clear sensitive data') and mentions related tools ('Pair with remember and recall'). This gives clear guidance on when to use vs alternatives, though it doesn't explicitly name a 'when not to use' case.
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.
Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer factual questions with subtle differences that are not immediately clear. Additionally, five polymarket tools cover similar ground (arbitrage, edges, fill risk, spread), making it hard to pick the right one without reading the full descriptions.
Tool names are consistently snake_case and mostly follow a verb_noun pattern (e.g., describe_cron, next_runs, validate_claim). Minor deviations exist (bet_research, entity_profile, pipeworx_trending) but the overall style is predictable and readable.
33 tools is well over the high end for a focused server, and the server name 'Crontab' implies a narrow cron utility while most tools are a broad data-research platform. This mismatch makes the count feel bloated and poorly scoped.
For a cron server, the set is severely incomplete: only describe_cron and next_runs exist, with no create/delete/update functionality. For the actual data-research domain, it is rich but lacks clear CRUD coverage for many resources, and the inclusion of unrelated cron/memory tools creates dead ends.