consolidate

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

With no annotations at all, the description carries the full disclosure burden and does so richly: it explains the 50-line cap, the events_remaining counter, whole-backlog vs. limited extraction, meaning-search embedding behavior, and the subtle case where facts_integrated: 0 can still produce written vectors. This is far beyond a generic 'consolidate' statement.

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 dense but well organized: a one-line summary, a when-to-call sentence, extraction mechanics, and embedding behavior. Every sentence contributes operational information, and the most important usage guidance is front-loaded.

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 having no output schema and no annotations, the description covers the key result fields an agent needs (events_remaining, facts_integrated, embedding) and refers to get_stats for store-wide coverage. It adequately equips the agent to call the tool correctly and interpret its results.

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?

Although schema coverage is already 100%, the description adds real semantics to both parameters: all: true means 'take the whole backlog in one call' and limit: N means 'the oldest N' unexamined lines. It also ties them to the extraction cap, which is not evident from the schema alone.

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 a concrete verb phrase, 'Copy, extract, and integrate,' then specifies exactly what the tool does: copies lines from named sources, extracts candidate facts, and integrates pending fact types (domains, entities, duplicates, contradictions, knowledge graph). This is specific enough to distinguish it from siblings like capture_fact and get_events.

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?

It gives explicit trigger conditions: 'Call this after capturing several facts, at a topic change, or before the conversation ends.' It also explains how to vary behavior with all/limit and points to get_stats for broader coverage, giving the agent clear directives on when and how to invoke it.

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