Godot MCP Bridge

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

With no annotations provided, the description carries the full burden. It discloses that the tool uses a template (behavioral trait), but fails to mention side effects like file system mutation, overwrite behavior, or return values.

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 extremely brief (two fragments) and front-loaded with the action verb. However, given the complete lack of schema documentation and the mutation nature of the tool, this brevity leaves critical gaps.

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 file creation mutation tool with no output schema, undocumented parameters, and no annotations, the description is inadequate. It lacks: parameter documentation, return value description, file path handling, and template specification details.

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 description coverage is 0% for both timeoutMs and autoConnect parameters, and the description adds no information about them despite the presence of additionalProperties: true which allows arbitrary shader configuration properties. The description mentions 'template' but doesn't clarify template selection parameters.

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 creates a shader file from a template, distinguishing it from siblings like edit_shader, read_shader, and assign_shader_material. The '(Compatibility tool)' tag adds specificity about its intended use case.

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 '(Compatibility tool)' label provides implicit guidance that this is for legacy or specific compatibility scenarios, but lacks explicit when-to-use advice or named alternatives like create_resource.

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