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 offers minimal insight. The 'Compatibility tool' hint suggests specific behavioral constraints but fails to explain them. It does not disclose what happens if the timeout expires, what gets 'auto-connected,' or whether the operation is reversible.

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 (one sentence plus parenthetical), which prevents bloat, but given the complete lack of schema documentation and behavioral annotations, this brevity results in underspecification rather than efficient communication.

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 with zero schema coverage, no output schema, and no annotations, the description fails to provide necessary compensatory detail. Critical gaps remain regarding parameter semantics, error handling, and the specific meaning of 'Compatibility tool.'

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?

The schema has 0% description coverage for 'timeoutMs' and 'autoConnect,' yet the description provides no semantic context for these parameters. The agent cannot infer what timeout is being measured (operation duration? connection timeout?) or what automatic connection refers to (signal connections? node parenting?).

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 core action (instancing a scene as a child node) and distinguishes it from sibling 'add_node' by specifying 'scene.' However, the parenthetical '(Compatibility tool)' is cryptic and unexplained, creating ambiguity about whether this is a legacy, deprecated, or special-purpose tool without clarifying the implications.

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 siblings like 'add_node,' 'create_scene,' or 'open_scene.' The description does not indicate prerequisites (e.g., whether the scene must be loaded first) or when instantiation should be avoided.

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