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 indicate destructiveHint=true and idempotentHint=true, so the description's 'Delete' aligns without adding new behavioral context. No contradiction, but little extra value beyond 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?
Two sentences, front-loaded with purpose and usage. Every sentence is essential and there is 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 tool with one parameter and no output schema, the description covers the action, purpose, and usage context adequately. It pairs well with sibling tools and is complete.
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% for the single parameter 'key'. The description does not add additional meaning beyond what the schema provides, so baseline score applies.
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 action ('Delete'), the resource ('previously stored memory'), and the method ('by key'). It also differentiates from siblings ('remember' and 'recall'), making it distinct.
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?
It provides specific scenarios for use: 'when context is stale, the task is done, or you want to clear sensitive data'. It also mentions pairing with related tools, giving clear guidance on when to use this tool.
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 includes multiple overlapping tools (ask_pipeworx variants, many polymarket tools) that serve similar purposes, and there is a sharp domain split between food tools and Pipeworx data tools, making it hard for an agent to choose correctly.
Tool names are inconsistent, mixing verb_noun (search_food), noun_verb (nutrition_analysis), prefixed (pipeworx_feedback, polymarket_arbitrage), and no pattern. Some use underscores, some use whole words.
34 tools is on the high side, and the scope is extremely broad (food, data queries, prediction markets, subscriptions), which could overwhelm an agent, but the number alone is not extreme.
As a food API server, it is missing key features like recipe details, ingredient substitution, or meal planning, while including many extraneous tools. The data analytics tools are extensive but not aligned with the server's stated purpose.