consolidate_session

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

With no annotations, the description bears full responsibility. It discloses core actions (promote, merge, summarize, extract) but lacks details on side effects, reversibility, or authorization needs. The behavioral information is present but incomplete.

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 sentences convey the purpose, steps, and distinction from a sibling tool. Every sentence adds 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?

While the description lists pipeline steps, it does not specify the output or return behavior (e.g., whether it returns a report or is void). Given no output schema, this is a gap in completeness for a multi-step pipeline.

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 is 100% for the single parameter (sessionId), and the description adds no further detail beyond the schema's description. Baseline 3 is appropriate.

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 provides a specific verb (Run) and resource (ConsolidationPipeline on a session), lists the pipeline steps (promote working memory, merge duplicates, summarize, extract patterns), and explicitly distinguishes from the sibling tool 'run_consolidation_now'.

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 contrasts this tool with run_consolidation_now, signaling when to use each: use consolidate_session for a full session-scoped pipeline, and run_consolidation_now for the dedup scheduler. However, it does not provide explicit when-not conditions or prerequisites.

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