delete_all_memories

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

No annotations are provided, so the description must disclose behavioral traits. It mentions using a safe bulk-delete instead of memory.delete_all(), but this is vague. It fails to describe error handling, reversibility, or permission requirements, leaving significant gaps in transparency.

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 concise with two sentences. The first sentence front-loads the core purpose. The second sentence includes an implementation detail ('NEVER calls memory.delete_all()...') that is somewhat extraneous and could be confusing, slightly reducing conciseness.

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 the tool's complexity (3 optional parameters requiring at least one filter) and the presence of an output schema, the description does not explain what happens when no filter is provided or what the return value indicates (e.g., number of deleted memories). It is incomplete for an agent to confidently invoke the 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?

The input schema has 100% coverage, so the descriptions of user_id, agent_id, and run_id are already clear as scope filters. The description adds the constraint that at least one filter must be provided, which adds meaning beyond the schema's default-null indicators. However, it doesn't elaborate on parameter usage beyond this.

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 bulk-deletes all memories within a given scope, using specific verbs and resources. It distinguishes itself from sibling 'delete_memory' by implying a bulk operation, and the requirement of at least one filter aligns with the input schema parameters.

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 a usage condition: 'Requires at least one filter.' This implies when to use the tool but does not explicitly compare it to alternatives like 'delete_memory' or provide when-not scenarios. The note about using safe bulk-delete gives behavioral context but not usage boundaries.

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