Godot MCP Bridge

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

No annotations are provided, so the description carries full burden. It fails to disclose movement behavior (instant teleport vs. interpolated motion vs. pathfinding), what happens on timeout, or what 'autoConnect' refers to. Only the cryptic 'Compatibility tool' suggests behavioral constraints.

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?

While brief and front-loaded with the action, the description is underspecified rather than appropriately concise. The '(Compatibility tool)' qualifier wastes space without explanation, and critical context is omitted to achieve brevity.

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?

Inadequate for a tool with 'additionalProperties: true' suggesting complex, dynamic inputs. No explanation of the extension mechanism, output behavior, or integration with the game engine (evident from siblings). Fails to leverage the lack of output schema by describing return values or side effects.

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%, yet the description provides zero compensation for the two parameters (timeoutMs, autoConnect). It does not explain what the timeout measures (movement duration? connection timeout?), what autoConnect connects to, or what valid 'additionalProperties' are accepted.

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?

States the basic action ('Move actor to target') but lacks specificity about what constitutes an 'actor' in this context (likely Godot given siblings) and fails to differentiate from similar tools like 'move_node' or 'navigate_to'. The '(Compatibility tool)' parenthetical is unexpanded.

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?

Provides no guidance on when to use this tool versus alternatives like 'move_node' or 'navigate_to'. The '(Compatibility tool)' hint suggests deprecation or legacy usage but does not specify what to use instead or when this is appropriate.

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