Godot MCP Bridge

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

No annotations are provided, so the description carries full burden. The only behavioral hint is '(Compatibility tool)' which suggests potential deprecation but lacks details on side effects, error handling, or atomicity. Does not clarify that the schema uses additionalProperties for the actual node/property 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?

The description is brief (two fragments), but given the complexity of the additionalProperties pattern, 0% schema coverage, and need for sibling differentiation, it is underspecified rather than efficiently concise. Every word earns its place, but there aren't enough words.

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?

With no annotations, no output schema, 0% parameter description coverage, the additionalProperties anti-pattern, and numerous similar sibling tools, the description fails to provide sufficient context for correct invocation. Critical gaps include the parameter passing convention and differentiation from sibling tools.

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 has 0% description coverage and uses additionalProperties: true to accept the actual node and property parameters, but the description fails to document this pattern or explain what parameters (node_path, property_name, value) should be passed via additionalProperties. Also does not explain timeoutMs or autoConnect.

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 (update) and target (node property) but fails to distinguish from similar sibling tools like set_game_node_property, batch_set_property, and cross_scene_set_property. Does not clarify whether this targets editor or game runtime nodes.

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 its numerous property-setting siblings. The parenthetical '(Compatibility tool)' suggests legacy status but fails to explain what that means or recommend modern alternatives.

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