delete

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It clearly explains the soft-delete nature: 'Does not remove the JSON record; it sets deletedAt.' This is a critical non-obvious trait that goes beyond a typical delete. However, it does not address edge cases like non-existent URIs or already-deleted memories, which slightly reduces completeness.

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 extremely concise at two sentences, front-loaded with the primary action, and every sentence adds value—purpose, behavior, and usage guidance. There is no redundancy or filler.

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 operation with two parameters and no output schema, the description covers purpose, usage guidance, and key behavioral context. It does not specify return values or error conditions, but these are not explicitly required given the lack of an output schema. Overall, it is adequately complete for an agent to invoke the tool correctly.

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?

The schema describes 'uri' as 'Exact memory URI' (50% coverage), and the description reinforces 'exact URI' and advises searching first if unknown, adding meaning to the uri parameter. However, the 'namespace' parameter remains unexplained, and the description does not fully compensate for the missing schema description for that parameter.

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 tool's action: 'Soft-delete an active memory by exact URI.' This is a specific verb+resource combination, and the additional explanation that it sets deletedAt rather than removing the JSON record distinguishes it from a hard delete and aligns with its sibling operations like create/update/read.

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 provides explicit guidance: 'Use search/list first if URI is unknown.' This names alternative tools and sets a clear precondition for use, helping the agent decide when to invoke this tool versus searching or listing first.

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