apply_crystals

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

The description indicates a write operation ('persist'), but with no annotations, it fails to disclose key behaviors such as whether files are overwritten, error handling, or any side effects. The output schema exists but is not referenced.

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 single sentence is very concise and front-loads the key purpose. However, it omits essential information that would justify expanding to 2-3 sentences.

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?

Despite only two parameters and an existing output schema, the description is too sparse. It does not specify the structure of crystals_json, the expected format of cluster_slug, or what the return value signifies, leaving the agent underinformed.

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?

With 0% schema description coverage and no parameter explanations in the description, the agent has no understanding of what 'cluster_slug' or 'crystals_json' represent, despite the latter being a complex nested object.

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 action ('Persist crystal answers') and the exact file path structure ('hub/<cluster>/crystals/<slug>.md'), making it specific and actionable. This distinguishes it from sibling tools that handle other cluster or paper operations.

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?

No guidance is provided on when this tool should be used versus alternatives like 'apply_cluster_rebind' or 'apply_cluster_summaries'. The description does not mention prerequisites, context, or 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.