Godot MCP Bridge

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

Identifies itself as a 'Compatibility tool' which hints at legacy/deprecated status, but with no annotations, the description fails to disclose critical behaviors: whether transforms are preserved during reparent, signal connection handling, or the meaning of 'timeoutMs' and 'autoConnect' 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 (single sentence with parenthetical). While efficiently structured, it is arguably too minimal given the complete absence of schema documentation and the complexity of node manipulation in Godot.

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 manipulation tool with zero schema coverage and no output schema. Fails to explain the 'Compatibility tool' implications, parameter purposes, or return behavior. The 'additionalProperties: true' flag suggests flexible input that desperately needs documentation.

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 accepts 'additionalProperties: true', yet the description provides zero parameter guidance. No explanation of 'timeoutMs' (unusual for a reparent operation), 'autoConnect', or what extra properties are permitted.

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 tool manipulates nodes via 'Move or reparent', but 'Move' is ambiguous (spatial vs. hierarchical) and fails to distinguish from sibling 'move_to'. The 'Compatibility tool' parenthetical adds context but doesn't clarify scope.

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 on when to use this versus 'move_to', 'duplicate_node', or 'delete_node'. Does not mention prerequisites (e.g., node must exist, target parent constraints) or when reparenting is preferred over other operations.

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