Apply GLSL TOP mapping

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses two critical behavioral prerequisites: TDMCP_RAW_PYTHON=on and TDMCP_BRIDGE_ALLOW_EXEC=1. This adds valuable execution-security context not present in annotations. It does not contradict the 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?

Three sentences, front-loaded with the core action, with no wasted words. It efficiently conveys the operation, requirements, and context.

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 build tool with no output schema, the description covers the essential operational context: what it builds, what inputs it needs, and environment requirements. It omits return value details and side effects on existing network state, but given the medium complexity, it is reasonably complete.

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 100%, so the input schema already explains all parameters. The description adds the qualifier 'pre-translated' and outlines the mapping contents (fragment + uniforms + channels + controls), but this adds marginal value over the schema's 'Pre-built mapping' description. Baseline 3 applies.

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 uses a specific verb ('Build') and resource ('self-contained GLSL TOP network') with a precise input ('pre-translated mapping'), making the tool's function immediately clear. It also distinguishes itself from sibling import tools by identifying as the 'foundation primitive' used by Shadertoy and ISF importers.

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 clear context: it is the underlying primitive for Shadertoy/ISF importers and is intended for power users with hand-translated fragments. It implies when to use directly versus through importers, though it does not explicitly name alternatives or exclude other tools.

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