delete_all_memories

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

No annotations are provided, so the description must carry the full burden for behavioral disclosure. It states the destructive action ('Delete all memories') but does not warn about permanence, irreversibility, or clarify the ambiguous 'and/or' scoping semantics (whether both scopes are AND or OR). This is a significant gap for a bulk delete operation.

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 action, and contains no filler. Every word contributes meaning, making it highly efficient.

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 bulk delete tool with two well-documented parameters and no output schema, the description covers the core essentials. However, it leaves out safety-related context (e.g., that deletion is permanent) and the precise scoping logic, which are important for a destructive operation. The absence of annotations elevates the need for such details.

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 100%, so the baseline is 3. The description adds value by specifying that at least one scope is required, a constraint not captured in the schema's 'required' array. It also clarifies that user_id and agent_id serve as scope filters, though the 'and/or' relationship could be more explicit.

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 'Delete' and resource 'all memories for a user and/or agent', clearly distinguishing it from the sibling 'delete_memory' by the 'all' qualifier. It also adds the scope requirement, making the tool's purpose unambiguous.

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 important usage constraint ('At least one scope is required') but does not explicitly state when to use this tool versus alternatives like delete_memory. The intended use case (bulk deletion) is implied rather than stated.

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