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, so the description's 'Delete' aligns with that. It adds context about clearing sensitive data but doesn't go beyond the annotation significantly.
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 with no wasted words. The action and resource are front-loaded, and usage guidelines follow immediately. Every sentence is necessary.
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 tool with one parameter and annotations present, the description covers purpose, usage, and relationship to siblings fully. No gaps.
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 description of the 'key' parameter ('Memory key to delete') does not add meaning beyond the schema definition. Baseline score of 3 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 uses a specific verb+resource ('Delete a previously stored memory by key') and distinguishes itself from sibling tools 'remember' and 'recall', clearly establishing its unique purpose.
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 ('context is stale, the task is done, or you want to clear sensitive data') and references sibling tools for pairing, providing clear guidance on 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.
Most tools have clearly distinct purposes, but there is some overlap between research-oriented tools like ask_pipeworx and deep_research, and between entity_profile and compare_entities. Descriptions help differentiate them, so overall an agent can tell them apart.
Tool names are inconsistent, mixing snake_case (ask_pipeworx, list_subscriptions) and camelCase (bag_research, compare_entities). There is no uniform naming pattern, which can be confusing.
With 35 tools, the set is too large for a server named 'Mastodon'. Only a few tools are actually Mastodon-related (e.g., get_account, get_timeline), while the majority are PipeWorx tools unrelated to the core purpose.
As a Mastodon server, the toolset is severely incomplete: it lacks basic social media operations like posting statuses, following/unfollowing, and engaging with content. The name misrepresents the actual capabilities.