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 cover destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the bar is lower. The description adds minor context ('previously stored', 'clear sensitive data') but doesn't disclose additional behavioral details like irreversibility or error handling. It is consistent with 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?
Three sentences, front-loaded with the core action, and every sentence adds value—purpose, usage trigger, and sibling pairing. No fluff.
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?
The tool is simple (one required param, no output schema) and annotations cover safety/destructive profile. The description includes purpose, usage guidance, and sibling relationships, making it complete for 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 description coverage is 100% ('Memory key to delete'), so the description doesn't need to compensate. The description's 'by key' is redundant with the schema, adding no extra meaning. 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?
The description uses a specific verb ('Delete') and resource ('previously stored memory by key'), clearly differentiating from siblings like 'remember' (store) and 'recall' (retrieve). It states exactly what the tool does.
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 the tool: 'when context is stale, the task is done, or you want to clear sensitive data'. Also names complementary tools ('Pair with remember and recall'), providing clear contextual guidance.
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.
Many tools have overlapping functionality (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and the set includes both food-specific feeds and general data tools without clear separation. Distinguishing between them, especially for an agent, would be difficult.
Tool names follow no consistent pattern: some are snake_case (list_feeds, read_feed), others are lowercase with underscores (ai_visibility_check), and many are multi-word without clear structure (polymarket_arbitrage, scan_dependency). This inconsistency makes it hard to predict tool names.
With 34 tools, the count is high, and most tools are unrelated to the server's stated purpose of 'Food Feeds'. The inclusion of general-purpose Pipeworx tools (e.g., deep_research, entity_profile, polymarket tools) makes the set bloated and unfocused.
For the food feeds domain, only three tools (list_feeds, read_feed, fetch_feed) are relevant, which is incomplete. The server lacks tools for searching, subscribing, or managing feeds. The presence of many unrelated tools does not compensate for this gap.