Godot MCP Bridge

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

With no annotations provided, the description carries full disclosure burden but offers only the 'Compatibility tool' label as behavioral context. It does not explain scope (project-wide vs node-specific), persistence, side effects, or why the parameters include connection-oriented names (timeoutMs, autoConnect) seemingly unrelated to color values.

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?

Extremely concise at five words. No filler content—every word conveys information, though the brevity severely under-serves the tool's complexity given zero schema documentation and no output schema.

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 domain complexity. Godot theming involves multiple property types (colors, constants, fonts, styles); this tool offers no explanation of the color property system, no output schema guidance, and no parameter documentation despite having two configuration options with defaults.

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 coverage is 0% for both parameters (timeoutMs, autoConnect), and the description completely fails to explain these parameters. The mismatch between the tool name (suggesting color theming) and parameter names (suggesting network/connection timeouts) creates confusion that the description does not resolve.

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 basic action ('Set theme color override') but lacks specificity about which color property or theme resource is targeted. Does not differentiate from siblings like set_theme_constant, set_theme_font_size, or set_theme_stylebox, leaving ambiguity about what constitutes a 'color' vs other theme properties in this context.

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. The parenthetical '(Compatibility tool)' hints at a specific use case but fails to explain what compatibility scenario warrants this tool over standard theme modification approaches.

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