Delete memory

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write operation. The description adds useful context beyond the annotations: the photos are preserved, only the memory entry is removed, and the side effect is removal from the server. It does not discuss irreversibility or permissions, but the destructive annotation covers the safety profile.

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 short and front-loaded with the core action and the key distinction about photos. The "Side effect: removes the memory from the server" sentence is somewhat redundant with "only the memory entry goes away," and the Args/Returns block is boilerplate, but the overall size is appropriate.

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?

This is a simple one-parameter destructive tool with annotations and an output schema, and the description covers the essential behavioral distinction that photos remain. The output schema handles return details, and the destructive annotation covers safety. The main gap is the lack of deeper parameter semantics and explicit usage exclusions, but the definition is largely complete for the tool's complexity.

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 for the single parameter. It only says "memory_id: The memory to delete," which largely restates the parameter name and title without adding format, example, or source information. The description does not meaningfully improve parameter understanding beyond the schema's type and title.

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 states a specific verb and resource ("Delete a memory") and immediately distinguishes it from photo deletion by clarifying that "The photos stay in the library — only the memory entry goes away." This separates it from sibling destructive tools such as delete_assets and delete_album.

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 implies usage by clarifying that only the memory entry is removed while photos remain, which helps an agent choose it when deleting a memory rather than underlying assets. However, it does not explicitly state when to use this instead of update_memory or delete_album, nor does it mention prerequisites or irreversibility beyond the annotations.

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