godot_create_shader

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

The annotations already indicate this is not a read-only operation, and the description adds the useful side effect of generating a matching material. However, it does not disclose other behaviors such as file overwriting, validation of code, or what happens when the material path is omitted. More transparency would be possible.

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, front-loaded sentence with no wasted words. It captures the essential purpose and the key side-effect without restating schema details.

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?

The definition is acceptable for a tool whose schema is rich, but it still leaves out guidance on when to use it relative to material-only or shader-validation tools. For a complex tool with several optional parameters and default behaviors, a little more context would improve the overall completeness.

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 free-text description doesn't explain any of the parameters, and the context indicates schema description coverage is 0%, so the description must carry more parameter meaning. It does not clarify how path, shader_type, code, create_material, or material_save_path interact, leaving the value of 'matching material' as the only parameter-related hint.

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 names a specific verb (create), a specific resource (custom Godot shader .gdshader), and a notable side effect (matching material). It is unambiguous, though it does not explicitly distinguish from siblings like godot_create_material or godot_validate_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 gives no guidance on when to use this tool versus alternatives. It does not say, for example, to use godot_create_material when only a material is needed or godot_validate_shader when the goal is validation. The usage context is only implied by the name.

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