Import ISF shader

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no additional behavioral context such as whether existing nodes are overwritten, permissions required, or side effects. For a tool that creates components, more transparency is needed beyond the bare annotations.

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 that is concise, front-loaded with the main action, and contains no unnecessary words. It efficiently conveys essential information.

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 (11 parameters, nested objects) and no output schema, the description is brief. It doesn't explain auto-generated controls, return values, or effects of optional parameters like channel_overrides. While the schema provides details, the description could be more complete about the outcome.

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 (~82%), so the description adds minimal value beyond summarizing the source parameter. It does not elaborate on any parameter intricacies, but it doesn't need to given schema richness. Baseline score of 3 is appropriate.

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 tool imports an ISF shader into TouchDesigner as a GLSL TOP with auto-generated controls, and specifies acceptable source types (raw, file, URL). It distinguishes from sibling shader tools by focusing on ISF format and auto-control generation.

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?

The description provides some context on acceptable source formats but does not discuss when to choose this over alternatives like import_shadertoy or create_glsl_shader. No explicit when-not-to-use or comparative guidance is given.

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