distill_session

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

No annotations are provided, so the description carries the full burden. It discloses the three-step process (microcompact, LLM summarization into 9 dimensions, extraction to RecallNest) and explicitly notes the side effect of persisting extracted memories. This goes beyond typical descriptions, though it lacks details on return values.

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 structured and front-loaded with purpose, followed by a breakdown of the three layers, a usage hint, and a side effect note. It is longer than some descriptions, but every sentence adds value and is not repetitive.

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 covers the tool's purpose, process, usage context, and side effects. With no output schema, it does not explain return values, but the tool's primary output is persistence, which is mentioned. It is reasonably complete for a tool of this complexity, though it could detail the 9 dimensions.

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 description coverage is 100%, so the baseline is 3. The description does not add parameter-specific meaning beyond what the schema already explains; it references the process (e.g., microcompact) but does not elaborate on any parameter semantics.

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 clearly states the verb 'distill', the resource 'conversation session', and the outcome 'structured knowledge' with persistence to long-term memory. It distinguishes itself from sibling tools like store_memory or distill_memory by naming RecallNest and the three-layer process.

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 gives an explicit usage trigger: 'Use when a session is ending or context is getting large.' It does not mention alternatives or when not to use, but the context provided is clear enough for an agent to decide.

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