Create shader from library

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

Describes behavior: creates GLSL TOP with live controls. Annotations confirm non-destructive and open-world. Could add more about what happens when 'expose_controls' is false, but overall clear.

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?

Two concise sentences, no filler, front-loaded with purpose. Efficient use of text.

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?

With 7 optional parameters and no output schema, the description sufficiently covers intent and usage. Distinguishes from sibling. Minor gap: could mention that tool creates a new node under parent_path.

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 coverage is high (86%) and descriptions in schema are detailed. Description adds value by explaining that speed/scale/color become live controls, enriching context.

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?

Clearly states the verb 'Instantiate' and resource 'curated...GLSL shader', lists specific shaders (tunnel, raymarch_sphere, etc.), and explicitly contrasts with sibling create_glsl_shader.

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?

Explicitly says 'unlike create_glsl_shader it ships robust built-in shaders rather than taking arbitrary code', guiding when to use this tool over alternatives.

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