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 readOnlyHint=false. The description's 'Delete' aligns with this, but adds little behavioral context beyond what annotations provide, such as permanence or side effects. No 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?
The description is concise and focused, with three sentences each serving a purpose: core function, usage scenarios, and companion tools. No unnecessary words or repetition.
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 tool with no output schema, the description adequately covers purpose and usage while leveraging annotations for safety context. It could mention irreversibility explicitly, but the destructiveHint annotation already conveys this.
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% with the parameter 'key' described as 'Memory key to delete.' The description does not add additional meaning beyond the schema, matching the baseline for full schema coverage.
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's function: 'Delete a previously stored memory by key.' It uses a specific verb and resource, and distinguishes itself from siblings like remember and recall by emphasizing deletion.
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 usage context: 'Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier.' It also suggests pairing with remember and recall, but does not explicitly state when not to use the tool, so it falls short of a 5.
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.
Several tools have significantly overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all perform data retrieval, with beta currently identical to stable. The polymarket_* family and bet_research also blur boundaries, and discover_tools vs suggest_questions both handle discovery. Despite detailed descriptions, agents are likely to misselect among these overlapping options.
All tools use snake_case, but conventions are mixed: some start with verbs (get_launch, search_launches, ask_pipeworx), others are noun phrases (entity_profile, pipeworx_trending), and there are versioned suffixes (ask_pipeworx_beta). While each domain group has internal consistency, the overall set lacks a unified pattern.
35 tools is excessive for a server named 'launches'—only 4 tools (get_launch, get_past_launches, get_upcoming_launches, search_launches) actually relate to space launches. The remaining 31 tools cover unrelated domains like prediction markets, company profiles, and memory, making the count inappropriate and diluting the server's focus.
For the claimed launch domain, the set provides only basic list/detail/search operations and lacks useful launch features like filtering by agency, date range, or launch site. More critically, the inclusion of 31 unrelated tools creates a fragmented surface with obvious dead ends—an agent expecting a launch-focused server would find most tools irrelevant.