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. It correctly identifies the 'runtime' context but fails to explain the critical 'additionalProperties: true' schema behavior—specifically that arbitrary property key-values are accepted alongside the defined timeoutMs/autoConnect parameters. The 'compatibility' claim is unexplained.

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), which is efficient but insufficient given the tool's complexity (arbitrary property setting). The parenthetical '(Compatibility tool)' wastes space without adding clarifying value. Core information is front-loaded but underdeveloped.

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 rich Godot ecosystem context (evident from siblings like 'godot_connect' and 'get_game_scene_tree'), the description fails to mention Godot or clarify how this tool differs from the 5+ other property-setting siblings. The lack of output schema and the presence of additionalProperties demands more explanation than provided.

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%, requiring the description to compensate. While 'multiple' implies arbitrary property acceptance (aligning with additionalProperties), the description completely omits what 'timeoutMs' and 'autoConnect' control, nor does it explain the expected format or naming of the node properties being set.

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 action ('Set') and resource ('runtime node properties'), distinguishing it from the singular sibling 'set_game_node_property' by specifying 'multiple'. The 'runtime' qualifier adds important context. However, the '(Compatibility tool)' parenthetical is cryptic and unexplained.

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 provides minimal guidance. The '(Compatibility tool)' hint suggests legacy usage but fails to explain when to use this tool versus alternatives like 'set_game_node_property', 'batch_set_property', or 'cross_scene_set_property'. No constraints or prerequisites are mentioned.

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