Godot MCP Bridge

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

With zero annotations, the description bears full responsibility for behavioral disclosure. It successfully indicates that children are duplicated, but omits critical details: where the duplicate appears in the scene tree, whether it shares resources with the original, what 'compatibility' limitations exist, and how naming conflicts are resolved.

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 at only two sentences, achieving front-loading of the core action. However, the extreme brevity contributes to information gaps rather than efficient communication, particularly regarding the unexplained 'compatibility tool' designation.

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 node duplication operation with no output schema. Missing: return value description (the new node reference), placement behavior in the scene tree, handling of attached scripts/signals, and explanation of the compatibility aspect. The 0% parameter schema coverage is not addressed by the description.

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%, and the description fails to compensate. It does not explain the `timeoutMs` or `autoConnect` parameters, nor does it clarify how to specify the source node identifier (likely expected via additionalProperties). The agent receives no guidance on required inputs despite the open-ended 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?

The description clearly identifies the verb (duplicate) and resource (node), explicitly noting that children are included in the operation. The parenthetical '(Compatibility tool)' adds contextual flavor but remains vague about specific compatibility constraints or deprecated status.

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?

No guidance is provided on when to use this tool versus alternatives like `add_node` or manual instantiation. The description fails to mention prerequisites (e.g., that a source node must exist) or when this compatibility tool should be preferred over native duplication methods.

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