delete_all_memories

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

No annotations provided, so description carries full burden. Clearly states destructive and irreversible nature, and behavior difference with/without agent_id. Pre-deletion recommendation adds context. Lacks mention of return value or side effects, but for a delete tool this is sufficient.

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?

Description is moderately verbose with bullet points and sections, but each part earns its place (use cases, caution, pre-deletion recommendations). Could be trimmed slightly, but front-loaded first sentence conveys core purpose.

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 no output schema and two optional parameters, description covers use cases, caution, and parameter behavior. Lacks detail on return value or default user_id, but sufficient for a destructive bulk operation. Siblings are well-differentiated.

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 100%, but description adds significant value: explains how agent_id filters to a session, and implies user_id defaults. Clarifies behavior beyond schema descriptions, enabling correct tool usage.

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?

Clearly states 'Bulk delete all memories for a user, optionally filtered to a specific session.' The verb 'bulk delete' and resource 'memories' are specific. Differentiates from sibling 'delete_memory' which deletes a single memory.

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?

Explicit use cases listed (fresh start, privacy wipe, cleanup, memory reset). Caution warns of destructiveness and irreversibility, advising confirmation. Recommends targeted delete as alternative, distinguishing from delete_memory.

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