consolidate

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

No annotations provided, so description carries full burden. It clearly states behavioral traits: the tool only adds a derived layer, never edits or deletes raw memories, includes a state-toggle guard for polarity clashes, and returns a report with specific fields. This provides comprehensive safety and behavior context.

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?

Description is detailed but not overly verbose. It is front-loaded with the main action and each sentence adds value. A minor reduction could improve conciseness, but it remains clear.

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?

Despite no output schema, the description lists report fields. No annotations, but safety and side effects are fully described. For a consolidation tool with one parameter, it provides complete context for usage.

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 has one parameter 'keep' (integer/null, default null). Description adds meaning: 'if keep is given) supersede the lowest-value surplus.' This explains the parameter's effect well, compensating for 0% schema description 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?

Description clearly specifies the verb 'Run', the resource 'ALL memories', and the actions: flag hubs, link near-duplicates, and optionally supersede surplus. It differentiates from sibling 'consolidate_clusters' by describing a broader 'dream' pass over all memories.

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?

While the description implies a consolidation pass over all memories, it does not explicitly state when to use this tool versus alternatives like 'consolidate_clusters' or other siblings. No direct guidance on when not to use it.

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