memory_repair

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

With no annotations, the description carries the behavioral burden. It does disclose that semantic notices are advisory and imposes read-both-memories and do-not-forward constraints, which is useful. But it never states whether operations like history cleanup or backup replay are destructive, reversible, or permission-gated, leaving the tool's overall side effects opaque.

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 first sentence packs an exhaustive comma-separated list of operations into a dense, ambiguous clause, while the second sentence contains essential usage and safety details. It is not overly long, but the structure buries actionability in a pile of items; a clearer mapping of task values to operations would be more effective.

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?

With two generic parameters, no annotations, and zero schema descriptions, the description alone is insufficient for a multi-purpose maintenance tool. It points to a help topic but omits concrete argument semantics, side effects, and sibling differentiation needed to invoke it correctly.

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 schema only shows generic task and data fields. The description demonstrates task="help" for notice handling but never enumerates valid task values or explains the data object at all, so an agent cannot reliably construct arguments for the listed operations.

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 frames the tool as a broad maintenance umbrella, listing many operations (evidence rebuild, conflict scans, duplicate sweeps, history cleanup, backup replay, notices, semantic runtime control) rather than a single specific verb+resource. It does not differentiate from sibling tools memory_review, memory_govern, or memory, so an agent would struggle to know exactly when this is the right tool.

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?

There is explicit guidance to use memory_repair(task="help") for notice handling and semantic_control actions, plus a caution to read both memories before dismissing or resolving and never pass a notice to judge or resolve_conflict. However, no guidance is given for the other listed maintenance tasks, and there is no 'when not to use' or comparison with sibling tools.

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