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 adds context about clearing sensitive data and addressing staleness, which is valuable 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 wasted words. Front-loaded with the core action, followed by usage guidance.
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 the simple single-parameter interface and rich annotations, the description fully covers what an agent needs: purpose, usage context, and relation to siblings.
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%, so description does not need to add much. The description does not repeat parameter details; baseline score 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 uses a specific verb 'Delete' and identifies the resource as 'memory by key'. It clearly distinguishes from sibling tools 'remember' and 'recall' by specifying 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?
Explicitly states when to use: 'when context is stale, the task is done, or you want to clear sensitive data'. Also mentions pairing with 'remember' and 'recall', providing 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.
Several tools occupy nearly identical roles: ask_pipeworx and ask_pipeworx_beta are described as functionally identical right now, ask_pipeworx_grounded and deep_research are overlapping query modes, and ai_visibility_check / scan_competitor_ai_presence / discover_tools / suggest_questions all blur into discovery or visibility tasks. The two actual BioStudies tools are clear, but they are buried in a server dominated by Pipeworx meta-tools.
All tool names use snake_case, and many follow a verb_noun shape such as search_studies, get_study, and discover_tools. However, the convention is inconsistent across the set: noun-first names like entity_profile and polymarket_edges, brand-prefixed names like pipeworx_feedback, and verb-first product names like ask_pipeworx all coexist, making the pattern harder to predict.
33 tools is well into the too-many range, and the count is especially inappropriate for a server named Biostudies since only search_studies and get_study actually belong to that domain. The rest form a sprawling general-purpose data-research platform that appears to have been merged into one server without a clear scope.
For the BioStudies-specific surface, search_studies and get_study provide reasonable read-only coverage for the EBI archive. But as the broader research platform the other 31 tools imply, the set is hard to evaluate for completeness because most actual data access is delegated to Pipeworx's hidden 5,718 tools rather than exposed directly, leaving notable gaps in transparency and direct source-level control.