godot_dispatch_compute_shader

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

The annotations give little positive information (all hints are false), so the description carries the burden of behavioral disclosure. It only says the shader is executed; it does not mention output buffer readback, resource allocation, side effects, or behavior on shader compilation failure.

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?

Single sentence with no filler; it is front-loaded with the main action and the API context is placed immediately after. Every word earns its place and the description is easy to parse.

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 schema and output schema provide most of the parameter and return-value context, and the description establishes basic purpose. What is missing is guidance on when this is the right tool, side-effect awareness, and any limitations of the RenderingDevice API path.

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 has 0% overlap with the schema parameters, mentioning none of them explicitly. The nested schema is rich with descriptions and defaults, but the tool description itself contributes no guidance for shader_code, input_buffers, workgroup_size, or even output behavior.

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 and specifically states the action: 'Execute compute shader on GPU' via the 'low-level RenderingDevice API'. It distinguishes itself from siblings like godot_validate_shader or godot_create_shader by communicating that this is an execution/dispatch operation, not a validation or creation tool.

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 use for low-level GPU compute dispatch, but it does not explicitly state when to use this over alternatives like godot_validate_shader or godot_set_shader_param. There is no mention of prerequisites or conditions that point the agent towards or away from this tool.

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