delete_memory

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states it deletes a memory but does not disclose irreversibility, permission requirements, or behavior when doc_id is not found. The return type is vaguely described as 'a dictionary with status and message' without specifics.

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 structured with Args and Returns sections. It contains no redundant sentences and is appropriately sized for a simple delete operation.

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 delete tool with one parameter, the description covers purpose, parameter, and return. However, with no annotations, it lacks important context about permanence and error conditions, making it only minimally complete. It does not reference the existing output schema (if any) or provide example usage.

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 has no description for doc_id (0% coverage). The description compensates by explaining 'The ID of the memory to delete', adding meaning beyond the schema's bare integer type. However, it does not specify format or constraints beyond that.

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 'Delete a memory by ID', using a specific verb ('Delete') and resource ('memory'), which distinguishes it from siblings like save_memory and update_memory. The scope is precisely defined by ID.

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?

No guidance is provided on when to use this tool versus alternatives. It does not explicitly state that this is for permanent removal or mention any prerequisites or conditions. Sibling tools (update_memory, query_memory) are not referenced as alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.