compile_shader

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds context that compilation can happen 'via Godot editor or local validation', which implies two modes of operation. However, it does not disclose potential side effects (e.g., reimporting modifies project state) or any prerequisites (e.g., whether editor must be running for editor mode).

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 that efficiently conveys the tool's purpose and mode. Every word contributes meaning, with no redundancies or filler.

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 tool with one parameter and no output schema, the description is mostly complete. However, it does not explain what the tool returns (e.g., success/failure or compilation errors) and does not clarify the difference from validate_shader, which is a nearby sibling. Given the simplicity, this is a minor gap.

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 coverage is 100% (the only param 'path' has a description), so the schema already documents the parameter. The description adds no further parameter semantics beyond the context of compiling a shader file.

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's function: 'Compile (reimport) a .gdshader'. It specifies the resource type (.gdshader) and the action (compile/reimport), and distinguishes itself from siblings like validate_shader (which may only validate) and write_shader (which writes content).

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 implies usage via 'Godot editor or local validation' but does not explicitly state when to prefer this over alternatives like validate_shader or editor_reimport_asset. It provides partial context but lacks clear when-to-use/when-not-to-use guidance.

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