Memory

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

With no annotations, the description carries the full behavioral-disclosure burden. It usefully discloses that delete removes data from memory and disk, reload resyncs after manual edits, search cascades with early stop, and stats are deduplicated, but it leaves many mutation actions unexplained and does not cover permissions, reversibility, or return behavior.

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 well-structured with clear headings and a scannable action list, and the length is broadly justified by the tool's complexity. However, the action list is incomplete relative to the schema and could be more tightly integrated with parameter meaning.

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 26-parameter, multi-action tool with no annotations, no output schema, and 0% schema description coverage, the description is not complete enough. It gives useful high-level framing but leaves out key action enum values and nearly all parameter-level invocation details.

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% across 26 parameters, so the description must compensate. It explains the action enum loosely and describes memory levels, but it omits several action enum values and provides no semantics for the many other parameters such as id, ids, query, content, path, confidence, or nested pattern/project fields.

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 identifies this as a unified memory system with a five-level cognitive hierarchy and enumerates its actions, so the general purpose is understandable. It does not distinguish the tool from nearby knowledge-related siblings such as mcp_m7_knowledge_hub or mcp_m7_knowledge_graph, which keeps it from 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?

The description lists actions but gives no explicit guidance on when to choose this tool versus alternatives, nor does it state prerequisites or exclusions. The action names imply possible uses, but the agent must infer usage conditions.

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