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 reveals nothing about return format (files, nodes, resource paths?), side effects, performance characteristics, or what 'Compatibility tool' implies regarding legacy behavior or deprecation status.

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?

While brief at only four words plus a parenthetical, the description is inefficiently terse—wasting no words but also failing to front-load critical information. The 'Compatibility tool' aside is cryptic and unexplained, adding confusion rather than value.

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?

For a tool dealing with scene dependencies (a complex concept in Godot involving packed scenes, external resources, and script references), the description is woefully incomplete. With no output schema, no annotations, and undocumented parameters, the description provides insufficient context for correct invocation.

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?

Input schema has 0% description coverage for its two parameters (timeoutMs and autoConnect). The description fails to compensate by explaining what these parameters control, their units (milliseconds for timeout), or why one would adjust the autoConnect boolean.

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 'Get scene dependencies' is a near-tautology of the tool name get_scene_dependencies, merely restating the verb and resource. While the parenthetical '(Compatibility tool)' adds minimal context, it fails to distinguish this tool from siblings like detect_circular_dependencies or analyze_scene_complexity, and does not explain what constitutes a 'scene dependency' in this context.

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 provided on when to use this tool versus alternatives such as detect_circular_dependencies, find_node_references, or get_scene_tree. The 'Compatibility tool' label hints at specific use cases but provides no explicit when-to-use or when-not-to-use criteria.

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