memcp_consolidate

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

In the absence of annotations, the description effectively discloses key behavioral traits: it merges, keeps the best insight, merges tags/entities, redirects edges, and deletes duplicates. It lacks explicit mention of whether the operation is destructive or reversible, but the core behaviors are clear.

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 concise, with a clear front-loaded summary followed by a parameter list. Every sentence earns its place; there is no redundancy or unnecessary information.

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 the complexity of a consolidation tool, the description provides a solid overview. It covers the main actions and parameters. Minor gaps include how the 'most accessed' default is determined, but overall it is sufficiently complete for typical use.

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 compensates well by explaining the role of each parameter (group_ids, keep_id, merged_content) in the docstring. This adds significant meaning 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 the tool's purpose: merging similar insights into one. It specifies the actions (keeping best insight, merging tags/entities, redirecting edges, deleting duplicates), making it distinct from sibling tools like memcp_remember or memcp_forget.

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 implies usage for merging multiple similar insights but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. There is no guidance on prerequisites or when consolidation is inappropriate.

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