Rememb

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

With no annotations provided, the description carries full burden for behavioral disclosure. It clearly indicates this is a destructive operation ('Delete ALL memory entries') and includes a safety warning ('Use with caution'), which are important behavioral traits. However, it doesn't specify whether this operation is reversible, what permissions are required, or what happens after deletion completes.

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 perfectly concise - two short sentences that each earn their place. The first sentence states the core functionality, the second provides crucial safety guidance. No wasted words, front-loaded with the most important information.

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 destructive tool with no annotations and no output schema, the description provides the minimum viable information. It identifies the destructive nature and includes a caution, but doesn't explain what 'memory entries' are in this context, what confirmation actually does, or what the expected outcome/response looks like. Given the high-stakes nature of deleting ALL data, more context would be beneficial.

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 schema has 100% description coverage with a single 'confirm' parameter that's well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, but with only one parameter and complete schema coverage, the baseline is high. The description's cautionary tone reinforces the significance of the confirm parameter.

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 action ('Delete') and target resource ('ALL memory entries'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'rememb_delete' - we can infer this deletes everything while 'rememb_delete' likely deletes specific entries, but this distinction isn't explicitly stated in the description.

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 clear contextual guidance with 'Use with caution' which signals this is a high-impact operation. It doesn't explicitly state when to use this versus 'rememb_delete' or other alternatives, but the 'ALL' qualifier and caution warning provide strong implicit guidance about appropriate usage scenarios.

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