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. Description adds context about clearing sensitive data and pairing, enhancing understanding beyond annotations.
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 with no fluff. Every part adds value.
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 no output schema, the description is fully sufficient. Covers purpose, usage, and 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?
Only one parameter (key) with schema coverage 100%. Description adds no additional semantic beyond schema description.
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?
Clearly states 'Delete a previously stored memory by key.' Specific verb+resource, and distinguishes from siblings (remember, recall).
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?
Explicit usage scenarios: stale context, task done, clearing sensitive data. Also advises pairing with remember and recall, providing clear 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.
Multiple query entry points have overlapping boundaries: ask_pipeworx and ask_pipeworx_beta are currently identical, suggest_questions and discover_tools both serve discovery/onboarding, and validate_claim overlaps with ask_pipeworx_grounded. With 34 tools including five Polymarket edge/scanner tools, an agent can easily select the wrong meta-tool despite the detailed descriptions.
All names are lowercase snake_case, so there is no style chaos, but the pattern is inconsistent: verb-led names like ask_pipeworx and validate_claim mix with noun-led names like entity_profile, recent_alerts, and polymarket_arbitrage, plus bare memory verbs like remember/recall/forget. Related tools are also not aligned, such as ai_visibility_check vs scan_competitor_ai_presence.
34 tools is too many for a server branded 'Data Toronto', and many tools are only loosely related to the core data-access purpose: ask_pipeworx_beta, generate_llms_txt, scan_dependency, ai_visibility_check, and the memory trio feel like bolt-ons. Even granting Pipeworx's broad research scope, the set is over-stuffed rather than well-scoped.
The data-research surface is unusually comprehensive: search, deep research, entity resolution/profiling, comparison, claim validation, alerts/subscriptions, and Toronto open-data querying are all covered. The main gaps are Toronto-side metadata details like resource schemas/columns and a way to browse the full dataset catalogue without a keyword.