reset_memory

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly communicates that the operation is destructive, affects all memories globally, is irreversible, and returns a confirmation of reset. This is comprehensive and unambiguous.

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 compact and well-structured, with the destructive warning front-loaded and critical details in short, scannable sentences. Every sentence adds essential information without 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 zero-parameter tool with an output schema, the description covers purpose, scope, when to use, irreversibility, and return behavior. No critical information is missing, making it complete for an AI agent to decide whether and how to invoke it.

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 tool has zero parameters, so there is no parameter semantics to explain. The baseline of 4 is appropriate because the description cannot add meaning beyond the empty schema, and nothing is missing.

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 opens with 'Reset the entire memory store' and labels it a 'DESTRUCTIVE operation,' giving a clear verb and resource. It further specifies that it deletes 'ALL memories in the backend, regardless of user/agent/app,' which distinguishes its global scope from targeted sibling tools like delete_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?

The description explicitly states when to use the tool: 'Only use this for testing or when you need to completely clear the memory store.' It also warns that the operation cannot be undone. It does not explicitly name alternatives or contrast with delete_all_memories, but the usage boundary is clear.

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