delete_memory

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

Without annotations, the description carries the behavioral burden and explains that the memory is removed from the server while photos remain in the library. This discloses the destructive scope and the non-destructive side effect, which is valuable for an agent deciding whether to invoke a mutation tool.

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 compact and front-loaded with the core action, followed by the key side effect, parameter documentation, and return clarification. Each sentence serves a distinct purpose, and there is no unnecessary elaboration.

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 one-parameter destructive tool, the description provides enough context: what is deleted, what is preserved, where the deletion happens, and what the response is. It does not discuss irreversibility or error cases, but the 'goes away' language sufficiently implies permanence.

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 description coverage is 0%, so the description must compensate. It documents memory_id as 'The memory to delete,' which, while minimal, is sufficient for a single required parameter and confirms its role beyond the bare schema property name.

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 identifies a specific action ('Delete a memory') and clearly separates 'memory entry' from photos, so the tool is not confused with photo/asset deletion. It also differentiates from sibling memory tools like create_memory and update_memory by stating the resource and effect precisely.

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 clearly communicates that this tool removes a memory while preserving photos, which tells the agent when to use it and explicitly what it does not do. It does not name alternative tools, but the exclusion of photo deletion provides clear contextual guidance.

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