distill_memory

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It correctly states 'Read-only — does not modify stored memories', which is important. However, it omits other behavioral traits such as rate limits, authentication needs, or output format details, leaving gaps.

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 only 3 sentences, each serving a clear purpose: stating the action and output, providing usage guidance, and noting read-only status. There is no redundancy or unnecessary information.

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 the tool's complexity (6 parameters, no output schema), the description is too brief. It does not explain the 'structured briefing' format or how this tool differs from closely related siblings like brief_memory or distill_session. The lack of an output schema makes this gap more significant.

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?

All 6 parameters have descriptions in the input schema (100% coverage), so the description does not need to elaborate on them. The description adds no new parameter-level meaning beyond what the schema provides. Therefore, a baseline score of 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 clearly states that the tool 'distills retrieved memories into a compact briefing', which is a specific verb ('distill') applied to a resource ('memories'). It also explicitly contrasts this with 'raw search results', indirectly distinguishing it from sibling tools like search_memory.

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 explicit usage context: 'Use this when you need a synthesized summary of stored knowledge on a topic rather than raw search results.' It also notes the tool is read-only. However, it does not explicitly name alternative sibling tools or provide when-not-to-use scenarios.

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