run_consolidation

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

No annotations are provided, so the description must carry the full burden. It discloses that merging keeps the most accessed/valuable representative, but does not mention destructive nature (loss of merged memories), permissions needed, or whether the operation is reversible. The dry_run parameter is mentioned in schema but not highlighted in description.

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 two sentences and contains no fluff. Every sentence adds value: first states purpose, second explains the merging logic and selection criteria.

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?

The tool has an output schema (not shown) and the description adequately covers the core functionality. However, being a mutation tool with no annotations, it lacks details on safety (e.g., reversibility, permissions, side effects). More context would be beneficial.

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 100%, so the schema already documents both parameters. The description adds context about keeping the most accessed/valuable representative but does not further explain parameter usage beyond what the schema provides. Baseline 3 is appropriate.

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 consolidates similar memories by merging near-duplicates, specifying the verb (consolidate/merge) and resource (memories). It distinguishes from siblings like preview_consolidation (which only previews) and run_cleanup (different 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 implies usage for merging duplicate memories but does not explicitly state when to use this tool versus alternatives like preview_consolidation or run_cleanup. There is no 'when not' guidance or mention of prerequisites.

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