memory_crystalize

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

With no annotations, the description fully carries the burden. It discloses that crystals survive session cleanup and appear in session_start, a key behavioral trait. It also mentions the return value is a digest. No contradictions or missing major behaviors.

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?

Four sentences with no redundant information. The most important action is front-loaded, and every sentence adds specific value: purpose, structure, survival, and usage timing.

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 no output schema, the description adequately describes the return value as a 'digest of what was crystallized.' It covers purpose, timing, lifecycle, and parameter hint. Minor gap: no explicit mention of what the crystal contains beyond grouping by category.

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 baseline is 3. The description adds value for the 'label' parameter: 'Auto-generated from date if omitted.' This clarifies behavior beyond the schema's 'Optional label'.

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 tool's purpose: 'Compress the last 30-50 sessions and auto-learned lessons into a dense Memory Crystal.' It uses a specific verb (compress) and resource (Memory Crystal), and distinguishes itself from siblings like 'memory_consolidate' and 'crystal_view' by focusing on creation of a summary.

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?

Provides explicit guidance: 'Run this monthly or after a big milestone to preserve institutional knowledge.' This tells when to use it. However, it does not mention when not to use or suggest alternatives, which would improve the score.

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