godot_validate_shader

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this tool compiles and checks for errors, but it does not reveal additional behavioral details such as whether the validation mutates project state or how errors are returned.

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 concise sentence that gets to the point immediately. There is no redundant wording, and the core action and resource are front-loaded.

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 read-only validation tool with rich schema, annotations, and output schema, the description is nearly sufficient. It clearly conveys the purpose and relies on structured fields for safety and return details; the main missing piece is explicit alternative guidance.

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 tool-level description does not add much parameter-level meaning. However, the input schema's property descriptions do cover shader_code, shader_path, and response_format, so an agent still has enough information to invoke the tool correctly with either inline code or a .gdshader file path.

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 names a concrete operation ('compile and check') and a concrete resource ('Godot Shader Language code'). This makes it easy to distinguish from sibling tools like godot_validate_script, which operate on a different resource type.

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 intended use case is implied: validating GDShader code for compilation errors. However, the description does not explicitly say when to prefer this over alternatives such as godot_validate_script, nor does it give guidance on inline code vs file-based validation.

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