athena_crystallize_output

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

With no annotations provided, the description carries the full burden of disclosing behavior. It mentions returning a crystal but does not clarify whether the tool mutates state, persists data, requires specific permissions, or has side effects. The phrase 'and RETURN' is ambiguous—does it return a value, or return to caller? This lack of behavioral context is a significant gap for a complex tool.

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, which is concise, but it is a dense run-on list with slashes and ampersands that is hard to parse. It lacks structure—bullet points or clearer separation would improve readability. It is appropriately short, but the content is packed awkwardly.

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 (18 parameters, nested objects, no output schema, no annotations), the description is severely insufficient. It provides no information about return values, error conditions, prereq prerequisites, or examples. An agent would have no way to understand the expected behavior or correctly invoke this tool beyond guessing from the name and schema.

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 0%, so the description must compensate by explaining parameters. It mentions concepts like math objects, graph/hypergraph deltas, and lexeme coordinates, which map roughly to some parameters (math_objects, edges, coordinates), but it leaves the six required parameters (semantic, text, native_locator, agent, task, seq) entirely unexplained. The description is too high-level to help an agent fill out the schema correctly.

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 a clear action—compile a visible output into an ATHENA crystal—and lists the major components included, which distinguishes it from generic finalization tools like athena_finalize_output. However, the heavy use of domain-specific jargon (KC144, JSPACE, polyatlas) may obscure the exact purpose for an agent unfamiliar with the ATHENA framework, preventing a perfect score.

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 to use this tool versus alternatives such as athena_finalize_output or athena_commit_delta. There is no mention of prerequisites, when it should be invoked in a workflow, or any explicit exclusions. The description only explains what it does, not when it is appropriate.

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