dakera_forget

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

With no annotations provided, the description carries full burden. It states deletion is permanent, immediate, and irreversible, which is transparent about consequences. It doesn't discuss permissions or side effects, but the key behavioral trait is well conveyed.

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 two sentences, front-loaded with the primary action, and every phrase adds value. No wasted words.

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?

Given 3 parameters, no output schema, and no annotations, the description covers the main functionality (two deletion methods) and provides an alternative. Missing: behavior when agent_id is missing (though required), and return value. Still fairly complete for a deletion tool.

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 coverage is 67% (agent_id lacks description). The description adds meaning by explaining memory_ids (exact removal) and tags (bulk delete), but fails to describe agent_id, leaving a parameter unexplained.

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 deletes memories by ID or tag, using specific verbs like 'permanently delete' and 'provide' for exact removal or bulk delete. It distinguishes itself by mentioning an alternative tool (dakera_memory_importance) for suppression, though it doesn't differentiate from the sibling dakera_batch_forget.

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 on when to use this tool (for permanent deletion) and when to prefer an alternative (dakera_memory_importance to suppress). However, it does not mention that agent_id is required, leaving a gap in prerequisites.

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