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. The description adds context about clearing sensitive data but does not describe additional behavioral traits beyond what annotations cover. No contradictions.
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?
The description is concise with two sentences: first defines purpose, second provides usage guidelines. No unnecessary words, front-loaded.
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 simple single-parameter schema and clear annotations, the description covers purpose, usage, and behavioral context. No output schema is needed for a deletion tool; the description 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 coverage is 100% and the parameter 'key' is described as 'Memory key to delete'. The description adds 'by key' but provides no additional meaning beyond the schema. 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 clearly states the tool deletes a memory by key, using the verb 'Delete' with the resource 'memory'. It distinguishes from siblings 'remember' and 'recall' by specifying it is for clearing stale or sensitive data.
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?
The description explicitly provides usage guidelines: 'Use when context is stale, the task is done, or you want to clear sensitive data'. It also pairs with 'remember' and 'recall', implying alternatives.
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.
Tool purposes are largely distinct across domains (Jira, data queries, prediction markets), but there is overlap within domains, e.g., ask_pipeworx vs ask_pipeworx_grounded and multiple Polymarket edge analysis tools.
Naming mixes multiple conventions: jira_ prefix, pipeworx_ prefix, polymarket_ prefix, and plain verbs (remember, forget, recall). No consistent pattern across the entire set.
34 tools is excessive for a server named 'Jira' which only has 4 Jira-specific tools. The majority are unrelated Pipeworx and Polymarket tools, making the scope bloated.
Jira-specific tools are incomplete (missing create, update, delete). While Pipeworx and Polymarket tools are comprehensive, they are out of place for a Jira server, leaving gaps in its stated purpose.