distill_memory

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

The description states it is read-only and does not modify stored memories, which is a key behavioral trait. However, without annotations, it does not disclose other behaviors like auth needs, rate limits, or output structure beyond 'structured briefing with citations'.

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 three concise sentences, each adding value: purpose, usage context, and return type plus read-only nature. No fluff.

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?

Given 6 parameters (all well-described in schema) and no output schema, the description adequately covers purpose, when to use, and a key behavior (read-only). It lacks comparison to similar tools like 'brief_memory' but is otherwise complete.

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%, so the description adds no extra meaning beyond the schema explanations for parameters like 'query', 'limit', 'scope', etc. Baseline score of 3 applies.

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 it distills retrieved memories into a compact briefing with source map, key takeaways, and reusable evidence, distinguishing it from raw search results. However, it does not explicitly differentiate from siblings like 'brief_memory' or 'distill_session'.

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 advises using this when a synthesized summary is needed rather than raw search results, but it does not explicitly name alternative tools or specify when not to use it.

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