wipe_project_memories

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

Clearly states irreversibility, immediate disk deletion, and what gets removed (vectors and metadata). No annotations provided, so description fully compensates by disclosing destructive nature.

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?

Three sentences: action+scope, consequences, usage guidance. No fluff. Front-loaded with key 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?

Single-parameter tool with output schema. Description covers purpose, usage, behavior, and parameter semantics comprehensively. No gaps given simplicity and existing structured fields.

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 already explains project_tag as namespace and global special case. Description adds context: 'namespace to wipe', examples, and clarifies scope. Adds value beyond schema despite 100% coverage.

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?

Description specifies exact verb ('Permanently delete') and resource ('all memories stored under project_tag'). Clearly distinguishes from siblings (search_memory, store_memory) by stating it's a destructive wipe operation.

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?

Explicitly states when to invoke ('only when the user has explicitly asked to clear or reset memory') and provides a caution ('when in doubt, confirm with user'). Also implies irreversibility, guiding appropriate use.

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