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. It discloses destructive behavior and the confirm requirement, but does not explain what 'in scope' means, whether the operation is reversible, or how it interacts with user_id/agent_id parameters. This is insufficient for a destructive action.

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 and concise, but it sacrifices necessary detail. While no sentence is wasted, the brevity leaves significant gaps, making it inadequate for the tool's complexity.

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 has 3 parameters, 0% schema coverage, no annotations, and an output schema, the description is severely incomplete. It fails to explain scope, parameter usage, or behavior, making it nearly useless for an AI agent.

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 description coverage is 0%, and the description adds no meaning to the three parameters. It only mentions 'confirm=true' without linking it to the confirm parameter. The roles of user_id and agent_id are entirely 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 verb 'Delete' and the resource 'all memories', which distinguishes it from the sibling 'delete_memory' that deletes a single memory. However, the phrase 'in scope' is vague and could be more precise.

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 mentions 'Requires confirm=true', which provides a necessary prerequisite but fails to advise when to use this tool versus alternatives like 'delete_memory' or 'search_memories'. No context on scope or user/agent filtering is provided.

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