crystal_melt

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 that squashing is deterministic and Zero-LLM by default, which is useful, but it omits key mutation details: whether intermediate nodes are deleted, whether the operation is reversible, what permissions are required, and what happens to existing artifacts or transitions.

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 a single sentence with no redundant filler and puts the core operation first. The jargon and parenthetical are dense, but the sentence is appropriately sized for a tool definition.

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?

For a non-trivial consolidation tool with five parameters, no annotations, and no output schema, the description is missing usage guidance and critical behavioral details about mutation and reversibility. The 100% schema coverage handles parameters, but the description should do more to explain the operation's context and consequences.

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 input schema already documents all five parameters. The description does not add any parameter-level meaning such as format, constraints, or examples beyond what the schema provides, which matches the baseline of 3 for high schema coverage.

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 names a specific verb pair ('Melt and squash') and resource ('intermediate sub-DAG transitions'), and states the resulting artifact ('single consolidated checkpoint node with aggregated artifact links'). It does not explicitly differentiate itself from close siblings like crystal_checkpoint or crystal_task_transition, but the core operation is clear.

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?

There is no guidance on when to use this tool instead of alternatives, nor any prerequisites or exclusions. The parenthetical 'Zero-LLM deterministic squashing by default' hints at a default behavior but does not tell the agent when to choose this over crystal_checkpoint or crystal_task_transition.

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