memcp_remember

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

No annotations are provided, so the description carries the full burden. It explains the basic action (save to persistent memory) but lacks details on idempotency, overwrite behavior, limits, or return values. The presence of an output schema mitigates this slightly, but the description itself could be more transparent.

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 a clear lead sentence, a usage paragraph, and parameter documentation. It is front-loaded, though the Args section is somewhat lengthy. Every sentence adds value, but slight trimming could improve conciseness.

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 8 parameters, 1 required, and no annotations, the description covers purpose, usage guidelines, and parameter semantics thoroughly. It does not explain return values, but the output schema likely handles that. The tool's complexity is moderate, and the description provides sufficient context for correct invocation.

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 0% schema description coverage, the description fully compensates by explaining each parameter in the Args section. It adds context: 'be concise but complete' for content, enumeration of categories, description of importance levels, and format guidance for tags and entities. This is highly valuable beyond the bare schema.

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 'Save an important insight to persistent memory' with a specific verb and resource. It distinguishes itself from sibling tools like memcp_recall (retrieval) and memcp_search, establishing its unique role as the write 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?

The description explicitly advises when to use: 'remember key decisions, facts, user preferences, or technical findings that should be preserved across conversations.' However, it does not explicitly state when not to use or mention alternatives, though the context of siblings implies read tools for retrieval.

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