Godot MCP Bridge

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

With no annotations provided, the description carries full disclosure burden but provides minimal behavioral context. It does not clarify what 'compatibility tool' implies for behavior (deprecated? limited scope?), what the return format is (no output schema), or why an 'inspect' operation has parameters named 'autoConnect' and 'timeoutMs' that suggest active connection behavior.

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 (5 words plus parenthetical), but brevity becomes a liability given the complete lack of schema documentation. The '(Compatibility tool)' aside consumes space without earning it—without explanation, it adds confusion rather than value. Structure is front-loaded but insufficient.

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 tool with zero schema documentation and no output schema. The description omits critical context: the meaning of 'compatibility tool', the nature of the returned signal data, the purpose of the autoConnect parameter (which is oddly named for an inspection tool), and how this relates to Godot's signal system evident in the 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 description coverage is 0% and the description completely fails to compensate. It does not explain what 'timeoutMs' refers to (connection timeout? inspection timeout?), what 'autoConnect' connects to (the node? a debugger?), or the significance of 'additionalProperties: true' allowing arbitrary extra properties. Parameters remain undocumented.

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 identifies the domain (node signals and connections) and implies a read-only operation ('Inspect'), but the parenthetical '(Compatibility tool)' is cryptic and unexplained. It fails to differentiate from siblings like 'find_signal_connections' or 'analyze_signal_flow', leaving ambiguity about when to use this specific tool.

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 the numerous sibling signal-related tools (find_signal_connections, analyze_signal_flow, connect_signal). The 'compatibility tool' label suggests specific constraints or deprecation, but offers no explanation of what those are or when this should be preferred/avoided.

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