Import Shadertoy

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

Annotations indicate readOnlyHint=false (creates) and destructiveHint=false (non-destructive). Description adds a useful behavioral note: macOS may prompt for outgoing connection on first fetch. No contradictions.

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 dense sentences with essential information front-loaded. No redundant 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?

Given 12 parameters, no required params, no output schema, and sparse annotations, the description covers core behavior (import, wire channels, controls, preview, offline option) sufficiently for an agent to decide to use it. Minor omissions (resolution, pixel_format) are secondary.

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 low (25%), but the description adds meaning for key parameters: wires iChannels (maps to channels), exposes Speed and optional Mouse controls (maps to expose_speed_control, expose_mouse_control), and captures preview (capture_preview). However, many parameters like resolution, pixel_format, provenance_override are not explained. Partially compensates for low schema coverage.

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 specifies the verb 'Build a GLSL TOP' from Shadertoy URL, ID, or pasted source. Distinguishes from siblings like import_isf_shader and create_glsl_shader by targeting Shadertoy specifically.

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?

Provides explicit when-to-use context: import via URL, ID, or pasted source. Mentions offline mode via raw_source and needing a key for reliable fetches. Though it doesn't directly compare with all siblings, the Shadertoy specificity implies differentiation.

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