delete_memory

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

No annotations are provided, so the description carries full burden. It discloses the audit trail behavior, which adds context beyond the basic delete action. However, it does not mention other behavioral traits like irreversibility, permission requirements, or effects on linked data.

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 with just two sentences. Every word serves a purpose: the first sentence gives usage guidance, the second defines function. 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 no output schema and three parameters (one required), the description adequately states the tool's purpose and usage guidance. However, it fails to explain parameter semantics, leaving a critical gap for proper invocation. The mention of audit trail adds some completeness, but parameter details are missing.

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 provides no information about the three parameters (id, cwd, reason). An agent cannot determine the meaning or proper values for cwd and reason from the description alone.

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 'Delete one memory with audit trail,' specifying the verb (delete) and resource (memory). It distinguishes from the sibling 'manage_memory' by advising preference to 'manage_memory action=delete,' making the unique purpose clear.

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 explicitly says 'Prefer manage_memory action=delete,' providing direct guidance on when to use this tool versus the alternative. This helps the agent decide which tool to invoke.

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