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. The description adds no new behavioral info beyond 'Delete', which matches annotations. No contradiction, but no added 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?
Two sentences, front-loaded with the core action, no wasted words. Highly concise.
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?
Given the tool's simplicity (single parameter, no output schema) and rich annotations, the description covers purpose, usage guidance, and relationships completely.
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% and description for 'key' is minimal ('Memory key to delete'). The description does not add meaning beyond the schema.
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 verb 'Delete' and the resource 'previously stored memory by key'. It distinguishes from sibling tools like 'remember' and 'recall' by explicitly being the deletion counterpart.
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 guidance on when to use ('context is stale, task is done, or clear sensitive data') and suggests pairing with 'remember' and 'recall', making the usage context very clear.
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.
Most tools have clearly distinct purposes, though the three ask_pipeworx variants (standard, beta, grounded) are very similar, potentially causing confusion. The Polymarket and memory tool families are well-differentiated.
All tool names use snake_case consistently, with a clear verb_noun pattern (e.g., resolve_entity, search_datasets, subscribe). No mixing of conventions.
34 tools is high but justified given the breadth of the Pipeworx platform and Ukraine Open Data integration. The set covers a wide range of data sources and operations without feeling bloated.
The tool surface is thorough, covering querying, comparison, profiling, subscriptions, and memory. Minor redundancy in ask_pipeworx variants, but no significant gaps for the stated data-access purpose.