dream

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It openly mentions side effects: 'may archive low-value entries and generate insight memories,' which indicates mutating/possibly destructive behavior. It also implies a threshold-based automatic behavior, though it does not detail the exact archiving process or reversibility. This is a solid disclosure for a maintenance utility.

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 compact and front-loaded: the first sentence states the core function, the second reveals side effects, and the third gives usage timing. All three sentences contribute unique value with no redundancy.

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 description gives a clear purpose, side effects, and usage context for a 2-parameter tool with no output schema. It could be slightly more specific about what 'archive' entails (e.g., whether memories are deleted or moved) and whether the operation is reversible, but the description is sufficiently complete for an agent to understand when and why to call it.

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?

The input schema already provides full descriptions for both parameters (force and scope) with 100% coverage. The tool description adds no parameter-specific information, so per rubric the baseline of 3 applies. The schema itself is self-explanatory regarding usage.

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 opens with 'Run a full memory consolidation cycle' which clearly specifies the action and resource, and enumerates the phases (Orient, Gather, Consolidate, Prune). It distinguishes itself from sibling memory tools by focusing on a holistic consolidation cycle rather than a single operation, and the side effects (archiving, generating insights) further clarify its unique role.

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 states when to use: 'Use when memory count is high and you need periodic maintenance.' This gives clear context for appropriate invocation, though it does not name specific alternatives or explicit when-not-to-use conditions. The trigger condition is meaningful and actionable.

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