preview_consolidation

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

Discloses non-destructive behavior ('without making changes') and that it shows clusters of similar memories. No behavioral contradictions; annotations not provided but description is adequate for preview functionality.

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?

Two concise sentences front-loaded with purpose and usage. No unnecessary words.

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?

Adequate for a simple tool: explains previewing clusters without changes. Output schema exists to detail return values, so description does not need to elaborate further.

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 covers parameter 'memory_type' with description. Description adds no new parameter-specific detail beyond schema, but does mention output (clusters) which is beyond parameter scope. Baseline 3 for high schema coverage.

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?

Clearly states the tool previews memory consolidation without making changes, showing clusters of similar memories that could be merged. Distinguishes from sibling tool 'run_consolidation' by indicating previewing nature.

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?

Explicitly recommends using this before running actual consolidation to review changes, providing clear context for when to use the tool.

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