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 set destructiveHint=true and readOnlyHint=false, but description adds context like 'clear sensitive data' and 'Delete', confirming destructive behavior without contradiction.
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, each serving a purpose: first declares the action, second gives usage conditions. No wasted words.
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 simple one-parameter destructive tool with full schema coverage and clear annotations, the description provides all needed context (usage, pairing, safety). Output schema is absent but unnecessary for a delete operation.
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 single parameter 'key' is described as 'Memory key to delete' in both schema and description. The description adds no significant extra meaning beyond the schema, so 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 'Delete a previously stored memory by key.' It specifies a precise verb (Delete) and resource (memory by key), and distinguishes from siblings by mentioning 'remember' and 'recall' as paired tools.
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 when-to-use: 'when context is stale, the task is done, or you want to clear sensitive data.' Also suggests pairing with 'remember' and 'recall', indicating alternative tools.
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, especially within their domains (e.g., Polymarket tools are well-separated). However, a few tools like ask_pipeworx, deep_research, and suggest_questions could cause minor confusion, as they all deal with querying data.
Tools from the same service use consistent prefixes (linear_, polymarket_, pipeworx_), but the overall naming style is mixed: some are verb_noun (linear_create_issue), some are noun_verb (bet_research), and some are single words (remember). This inconsistency reduces predictability.
With 35 tools, the server covers a broad range of functionality (data query, prediction markets, memory, etc.). While not excessive, the count is on the higher side, and the server name 'Linear' suggests a narrower focus, which may mislead expectations.
The tool set covers core data querying, research, entity profiles, prediction market analysis, and memory operations comprehensively. Minor gaps exist (e.g., limited Linear CRUD), but the overall surface feels complete for its intended use as a data assistant.