Godot MCP Bridge

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

No annotations provided, so description carries full burden. Fails to disclose blocking behavior, error handling, script sandboxing limits, or what 'Compatibility tool' implies (deprecated? legacy support?). Does not explain the 'autoConnect' parameter's connection target or timeout behavior.

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?

Severely under-specified for a tool involving script execution with timeout and connection parameters. The '(Compatibility tool)' parenthetical adds cryptic metadata without value. Extreme brevity here represents missing information, not efficient 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 a mutation-capable tool with no annotations and no output schema. Missing: return value format, error conditions, required game state (must be running?), and script input methods (how is the script passed? via additionalProperties?).

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 no compensation. Silent on 'timeoutMs' (what happens at timeout?) and 'autoConnect' (connect to what?). Ignores 'additionalProperties: true' entirely, leaving the agent unaware of the schema's open-ended parameter acceptance.

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 (execute script) and context (game vs editor), distinguishing it from sibling 'execute_editor_script'. However, 'Compatibility tool' is unexplained jargon, and the description lacks specificity about what the script can access or modify in the game runtime.

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?

Implied usage exists via 'game context' differentiation from 'execute_editor_script', suggesting use for runtime automation over editor tooling. Lacks explicit when-to-use guidance, prerequisites (e.g., running game instance), or warnings about side effects.

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