shader

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

Minimal behavioral context beyond listing actions. Annotations are not contradicted, but the description doesn't disclose side effects, permissions, or limitations of actions like create/write.

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?

Very concise but poorly structured. The action list is in inline code format, which is terse but not easily readable. It could be more organized.

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?

Despite having an output schema, the description omits return value info, error handling, and prerequisites. With 5 parameters and multiple actions, it is incomplete.

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 describes all parameters, so baseline is 3. The description adds no extra meaning; it only enumerates actions without linking to parameter usage.

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 it's for Godot shader management and lists specific actions. However, it doesn't differentiate from sibling tools like 'scenes' or 'scripts', but the purpose is clear enough.

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?

No guidance on when to use this tool versus alternatives. It defers to the help tool ('Use help tool for full docs'), indicating the description itself is insufficient for usage decisions.

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