memory_delete

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is conveyed structurally. The description adds isolation-by-project_path context and a note about runtime backend reporting, but stays silent on what happens when the key is absent and whether deletion is recoverable — meaningful gaps for a destructive mutation.

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?

Core action and lookup semantics are front-loaded in the first sentence. The trailing clause about runtime embedding/storage backend is somewhat tangential to a delete operation, keeping it below 5.

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, the description covers scope and isolation, and annotations handle the safety signal. However, with no output schema, the description should say what a successful delete returns or how a missing key is handled; it does neither.

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 100% schema description coverage the schema already documents all three parameters, including the namespace default and the 'absolute path to existing project directory' constraint. The description's phrase 'exact (namespace, key)' adds the matching-semantics nuance but little else. Baseline 3 applies.

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?

States a specific verb and resource ('Remove a stored memory entry') and pins the lookup mode to 'exact (namespace, key)', which implicitly separates it from the fuzzy memory_search sibling. It never names a sibling explicitly, so it falls short of a 5.

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?

'Use for project-scoped persistent memory. Never import personal memory automatically' gives some scoping context, but never says when to prefer this over memory_store/memory_search or whether a lookup should precede deletion. Usage is implied rather than prescribed.

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