emit_crystal_prompt

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

With no annotations provided, the description must fully convey behavioral traits. It only says 'emit', implying a generation operation, but does not disclose whether it is read-only, requires permissions, has side effects, or what the output format is. The lack of transparency is a significant gap.

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 short sentence, which is concise but sacrifices detail. It is front-loaded but underspecified. An appropriately sized description would include more context without being verbose.

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?

The description fails to explain the output (despite an output schema existing), the role of parameters, or the overall workflow. Given the complexity of generating a prompt for crystal generation, more context is needed for the agent to use it correctly.

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?

The input schema has 0% description coverage, and the tool description provides no explanation of the parameters (cluster_slug, question_slugs). The description does not compensate by adding meaning beyond the parameter names, leaving the agent to guess their roles.

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 states it emits a markdown prompt for generating crystals, which is a specific verb+resource. However, the phrasing is somewhat convoluted ('the calling AI should answer to generate crystals') and lacks clarity on what the prompt is for. It distinguishes from siblings like emit_assignment_prompt but could be more precise.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., emit_assignment_prompt), nor does it specify prerequisites, context, or exclusions. This leaves the agent without guidance on proper invocation.

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