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 and idempotentHint. Description adds context about sensitive data and memory nature, but does not detail behavior on missing keys or side effects.
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 concise sentences: first states action, second provides usage guidance and sibling references. No redundant or unnecessary 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?
Given a simple tool with one parameter and adequate annotations, the description fully covers purpose, usage context, and tool relationships.
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 provides 100% coverage for the only parameter (key). Description does not add extra meaning beyond what schema already states.
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?
Clear verb ('Delete') and resource ('previously stored memory by key'). Distinguishes from siblings by naming '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?
Explicitly states when to use: stale context, task done, clear sensitive data. Also suggests pairing with siblings, though no explicit when-not-to-use.
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 tool clusters have unclear boundaries. `ask_pipeworx_beta` is explicitly described as currently identical to `ask_pipeworx`, `discover_tools` overlaps with `suggest_questions`, and the six Polymarket tools (`bet_research`, `polymarket_edges`, `polymarket_arbitrage`, etc.) blur together for opportunity-finding. An agent would struggle to pick the right tool without reading every description carefully.
Naming is overwhelmingly consistent snake_case with a verb_noun or noun pattern (`ask_pipeworx`, `list_subscriptions`, `validate_claim`, `recent_changes`). The `polymarket_*` and `ask_pipeworx_*` families follow clear conventions. Minor deviations like `bet_research`, `entity_profile`, and `landprice_points` being noun-first are still readable and predictable.
32 tools is heavy for a server named 'Landprice' when exactly one tool (`landprice_points`) actually concerns land prices. The vast majority of tools constitute an unrelated general-purpose data research and prediction-market platform, making the count feel bloated and scattershot relative to the server's stated purpose.
For the actual broad scope revealed by the tools — structured data lookup, grounded verification, deep research, entity resolution, comparison, monitoring, and memory — the surface is reasonably complete with no obvious dead ends. However, for the 'Landprice' domain implied by the server name, coverage is nearly absent: only Japan is covered, with no other countries, address search, or property-level data.