Delete a stored preference

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

The description adds 'permanently' to the delete operation, conveying irreversibility beyond the destructiveHint annotation. It also clarifies the scope ('one memory by id') and that the deletion targets a single stored preference. No contradictions with the annotations were found.

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 short sentences, each earning its place: one states the action and target, the other states when to invoke the tool. No filler or redundant information is present, and the content is front-loaded with the core 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 single-parameter destructive tool with full schema coverage and relevant annotations, the description is complete. It covers what the tool does, when to use it, and the permanence of the action. No output schema exists, and none is needed for such a simple operation.

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 100%, and the schema already explains that id is the 'Memory id, as shown by recall.' The description only says 'by id,' adding no new meaning beyond the structured schema. Baseline 3 is appropriate because the schema fully documents the 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 uses a specific verb and resource: 'Permanently delete one memory by id.' It clearly distinguishes the tool from siblings like remember, recall, and search_knowledge by defining its exact operation. The title and description are largely consistent, with 'preference' as the stored memory item.

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 an explicit trigger: 'Use when the user says a preference is wrong or obsolete.' It does not explicitly name alternative tools or state when not to use this tool, but the given condition is specific and actionable. The context signals and sibling list allow an agent to infer that remember or recall are the alternatives, but they are not named.

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