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 idempotentHint=true. The description adds context about clearing sensitive data but does not disclose additional behavioral traits beyond what annotations provide.
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 redundancy. The description is front-loaded with purpose and efficiently covers usage and complementary tools.
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 single-parameter tool with good annotation coverage, the description is complete: it explains what it does, when to use it, and how it relates 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% and the schema already describes the 'key' parameter. The description adds no extra meaning beyond 'by key', so it does not compensate beyond the baseline.
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 verb 'Delete' and the resource 'memory by key'. It distinguishes from siblings by mentioning 'remember' and 'recall', which are complementary 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?
The description explicitly lists three use cases: stale context, task done, or clearing sensitive data. It also recommends pairing with remember and recall.
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.
Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer queries, and the multiple polymarket_* tools scan for edges and arbitrage. The Drive tools are distinct, but the surrounding 31 unrelated tools create significant ambiguity about which tool to call for a given task.
Tool names are all snake_case, but the pattern is inconsistent: some start with verbs (drive_create_file, ask_pipeworx, validate_claim), some are noun phrases (entity_profile, recent_changes, polymarket_edges), and some are bare verbs (remember, forget, recall). There is no uniform verb_noun convention, and suffixes like _beta and _grounded add further irregularity.
36 tools is far too many for a server named Google_drive, especially since only 5 tools (drive_create_file, drive_get_content, drive_get_file, drive_list_files, drive_search) actually relate to Drive. The other 31 tools cover unrelated domains like Pipeworx data queries, Polymarket betting, and memory management, making the tool count wildly disproportionate to the server's apparent purpose.
For a Google Drive server, the tool set is incomplete: it covers create, get content, get metadata, list, and search, but lacks essential operations like updating, deleting, uploading, moving, copying files, creating folders, or managing permissions/sharing. These gaps would force agents to work around missing core Drive functionality.