Godot MCP Bridge

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

No annotations are provided, yet the description discloses no behavioral traits. It does not explain where input is directed (game vs editor), whether events persist between frames, what the timeoutMs parameter controls, or what autoConnect connects to. The safety profile and side effects are completely undocumented.

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 at two fragments, the description is insufficiently informative given the complete lack of schema documentation. The '(Compatibility tool)' phrase consumes space without clarifying its meaning, and the front-loading prioritizes brevity over necessary context for a 2-parameter automation tool.

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 tool's apparent role in Godot automation (injecting keyboard events) and the presence of connection-oriented parameters, the description lacks critical context: key format expectations, target window/editor state requirements, and interaction with the engine's input queue. No output schema exists to compensate for these gaps.

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?

With 0% schema description coverage for both timeoutMs and autoConnect parameters, the description completely fails to compensate. It does not explain that timeoutMs likely controls connection timeout (default 5000ms) or that autoConnect likely handles automatic server connection, leaving critical parameters 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 provides a clear verb ('Simulate') and resource ('keyboard input'), establishing the basic function. However, it fails to distinguish this tool from sibling 'simulate_action' or 'simulate_sequence', leaving ambiguity about whether to use key codes, scan codes, or input action names.

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 parenthetical '(Compatibility tool)' cryptically implies this may be legacy or secondary to other methods, but provides no explicit guidance on when to use it versus 'simulate_action' or what 'compatibility' refers to. No prerequisites, exclusions, or alternatives are documented.

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