consolidate

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

Discloses auto-check conditions and difference between auto=True (lightweight) and auto=False (full explicit). No annotations exist, so description carries full burden. Could mention side effects (e.g., deletion of original observations).

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?

Three sentences; first sentence states core purpose, subsequent sentences detail auto flag behavior. Efficiently front-loaded, though could tighten wording.

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?

Covers auto mechanism and thresholds, but omits parameter details (sid, days, dry). Has output schema, so return values may be defined there, but parameter lack reduces completeness.

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 coverage 0% and description only mentions 'auto' parameter (default=True). No explanation for sid, days, or dry parameters, leaving agent guessing their meaning and 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?

Clear verb-resource pairing: 'Distil unconsolidated observations into structured memory layers.' Distinguishes from sibling tools (admin, search, session, etc.) which are unrelated.

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?

Describes two modes (auto=True/False) with explicit conditions for auto-trigger (e.g., >20 unconsolidated obs, obs older than 7 days). No explicit 'when not to use', but conditions clarify appropriate contexts.

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