eisenscript_reference

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

With no annotations, the description carries the full burden. It usefully discloses the 'libssynth backend' and that timeout-avoidance guidance is included, which is real context, but it never states that the tool is a side-effect-free static lookup, how large the returned text is, or that it requires no engine state. An output schema exists, so return structure is covered elsewhere.

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?

A single front-loaded sentence that names the resource first and then lists coverage. Every clause earns its place; the only flaw is the slightly fragmented list phrasing, which reads more like a table of contents than prose.

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 zero-parameter static reference with an output schema and no annotations, the description gives enough: what it contains and what backend it targets. A sentence on when to reach for it over validate_script or analyze_script would close the remaining gap.

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 tool takes zero parameters, so the baseline of 4 applies. There is no parameter meaning the description needs to disambiguate, and nothing it says misleads on inputs.

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 artifact (an EisenScript language cheat sheet) and enumerates its coverage areas: primitives, transformations, modifiers, preprocessor, and timeout tips. It is clearly a static reference resource, distinguishable in kind from action siblings like validate_script or render_script, though it never says explicitly it is a documentation lookup rather than a script operation.

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?

Usage is only implied: an agent can infer it should read this before authoring or debugging EisenScript. There is no explicit 'use this when...' guidance, no mention of pairing it with validate_script or preview_script, and no statement of when it is unnecessary.

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