Godot MCP Bridge

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

No annotations provided, so description carries full burden. 'Create' implies mutation but lacks specifics on persistence, side effects, or what 'compatibility' mode entails. Does not explain why creation requires timeout/auto-connect parameters.

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 terse (two fragments) but given the complete lack of parameter documentation and behavioral context, this brevity represents under-specification rather than 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 resource creation tool with mysterious parameters and no output schema. Missing: how to reference the created theme, what the compatibility warning means, and why network-like parameters exist on a theme creation tool.

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), yet description adds no explanation for these seemingly connection-related parameters in a theme creation context. Complete failure to compensate for undocumented schema.

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 it creates a 'theme resource' which is specific in the Godot context (evidenced by sibling tools like set_theme_color), but the '(Compatibility tool)' parenthetical is unexplained and creates ambiguity about whether this is deprecated or for specific use cases. Does not clarify distinction from generic create_resource sibling.

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 create_resource or add_resource siblings. The 'compatibility' label suggests specific usage constraints but fails to explain what they are.

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