Apply a GLSL shader from the vault

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

Annotations already indicate a non-read-only, non-destructive mutation with external interaction. The description adds the vault requirement and the note format, but does not disclose error handling, name collision behavior, or validation details, leaving some behavioral gaps.

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 extremely concise with two sentences: the first explains the core action and required note format, the second states the prerequisite. Every sentence adds value, and it is front-loaded with the main purpose.

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 absence of an output schema, the description could mention what the tool returns (e.g., the created GLSL TOP). However, it sufficiently explains the input format and prerequisite, making it mostly complete for a tool with good parameter schema coverage.

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 description adds meaningful context beyond the schema by specifying the expected structure of the shader note (fragment block, vertex block, frontmatter). This helps the agent understand how to format the 'note' parameter, complementing the parameter descriptions that already have 100% 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?

The description clearly states the tool reads a shader note from the Obsidian vault and creates a GLSL TOP. It specifies the exact format expected (glsl fragment block, optional vertex block, and frontmatter), distinguishing it from other creation tools like 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?

The description mentions a prerequisite (TDMCP_VAULT_PATH) but does not explicitly state when to use this tool over alternatives like create_glsl_shader. The context of siblings implies a distinction but lacks explicit guidance on when-not or alternative tools.

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