memory_lucidity_purge

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

No annotations are provided, so the description must fully convey behavioral traits. The description states it deletes data (destructive) but lacks details on irreversibility, need for confirmation, or impact on related data. For a purge operation, more explicit warnings about data loss are expected.

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 extremely concise: two sentences and a parameter list. It front-loads the core purpose ('Emergency purge') and immediately specifies scope. Every sentence adds value with no redundancy.

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 destructive nature and lack of annotations or output schema, the description should warn about consequences, confirm irreversibility, or specify whether the operation is logged. It only states the basic action and parameters, leaving safety considerations unaddressed.

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?

With 0% schema description coverage, the description must compensate. It explains the 'hours' parameter as 'How many hours back to purge (default 24)' and identifies 'user_id' as a user identifier. However, both parameters have defaults, and the description does not clarify if the purge is per user or global, or the format of user_id.

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's purpose: 'delete all data from the last N hours' with an 'Emergency purge' label, specifying both the verb (delete/purge) and the resource (data in a time range). This distinguishes it from sibling tools like memory_forget or memory_cleanup by emphasizing the time-based bulk deletion and urgency.

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 term 'Emergency purge' implies a constrained use case, but there is no explicit guidance on when to use this tool versus alternatives like memory_forget (which may delete specific memories) or memory_cleanup (which may be less destructive). No 'when not to use' or prerequisites are provided.

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