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 disclosure burden but only offers the cryptic '(Compatibility tool)' hint regarding behavior. It omits critical mutation details such as whether assignment overwrites existing materials, error handling if the node is invalid, or the implications of `additionalProperties: true` in the schema.

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 terse with zero filler words, consisting of a single functional sentence and a parenthetical qualifier. While efficient, it is arguably too brief given the complete absence of schema documentation, though the sentences themselves are well-structured and 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?

Given the 0% schema coverage and lack of annotations, the description is insufficiently complete for an agent to invoke confidently. It covers the high-level purpose but omits parameter semantics, side effects, and the specific meaning of 'Compatibility tool,' which are necessary for correct usage when no structured metadata exists.

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%, and the description completely fails to compensate by explaining the two parameters (`timeoutMs` and `autoConnect`). The agent has no semantic guidance on what 'autoConnect' refers to (shader graph connections? material-to-node linkage?) or typical timeout scenarios, leaving the parameters effectively undocumented.

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 core action (Assign) and specific resource type (ShaderMaterial) to a target (node), distinguishing it from sibling tools like `set_material_3d` or `set_shader_param` which handle generic materials or parameter updates. However, it lacks explanation of the '(Compatibility tool)' qualifier, leaving ambiguity about its specific scope versus modern alternatives.

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)' parenthetical implies legacy usage but fails to explicitly state when to use this tool versus `set_material_3d` or other material-related siblings. No guidance is provided on prerequisites (e.g., node existence, material readiness) or exclusions.

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