Godot MCP Bridge

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to deliver. It does not explain the connection behavior implied by 'autoConnect', the timeout implications, whether the operation is read-only, or what the return format contains. The 'compatibility tool' mention hints at behavior but remains cryptic.

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 appropriately brief and front-loaded with the core action. The two fragments are information-dense with no filler words. However, it verges on under-specification rather than optimal conciseness given the lack of schema documentation.

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?

Given the 0% schema coverage, absence of annotations, and lack of output schema, the description should elaborate on parameters, return values, and side effects. It provides none of these, leaving critical gaps in the agent's understanding of how to invoke the tool successfully.

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% for both parameters (timeoutMs and autoConnect), and the description offers no compensating information about their semantics, valid ranges, or usage patterns. While the parameter names are somewhat self-descriptive, the description fails to clarify the connection protocol or timeout behavior.

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 states the specific action ('Get') and resource ('runtime scene hierarchy'), effectively distinguishing it from the sibling 'get_scene_tree' tool (implied by 'runtime' vs editor context). However, the '(Compatibility tool)' suffix is unexplained jargon that slightly obscures the purpose.

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?

The description provides no explicit guidance on when to use this tool versus alternatives like 'get_scene_tree' or 'get_game_node_properties'. The '(Compatibility tool)' label implies a specific use case but fails to explain what compatibility scenario warrants its use over standard tools.

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