Godot MCP Bridge

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

With no annotations provided, the description carries full burden but only offers the cryptic '(Compatibility tool)' note. It fails to disclose critical behavioral traits: the schema allows arbitrary additional properties (additionalProperties: true), the tool likely spawns a game window/process, and it doesn't indicate whether the call blocks or returns immediately.

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 and front-loaded, consisting of a single sentence and a parenthetical. While efficient in word count, the extreme brevity contributes to under-specification rather than effective communication.

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 the tool's complexity. With two undocumented parameters, a flexible schema allowing arbitrary properties, no output schema, and no annotations, the description provides insufficient context for safe and effective invocation. The 'Compatibility tool' note raises questions it doesn't answer.

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. Critically, it fails to explain the significant schema flexibility indicated by 'additionalProperties: true', which allows arbitrary extra arguments—a major behavioral quirk that demands documentation.

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 (Run scene) and location (from editor), but 'from editor' is ambiguous and doesn't distinguish from siblings like 'run_test_scenario' or 'execute_game_script'. The '(Compatibility tool)' label adds minimal context without explaining what compatibility is being maintained.

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 the numerous execution alternatives (run_test_scenario, execute_game_script, simulate_action, etc.). The 'Compatibility tool' parenthetical hints at a specific use case but fails to articulate when this should be preferred or avoided.

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