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. It mentions '(Compatibility tool)' without explaining what compatibility constraints or behaviors this implies, and fails to describe side effects, state changes, or the significance of the 'autoConnect' parameter implied by the schema.

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 (two short sentences). While efficient in word count, the '(Compatibility tool)' fragment consumes space without adding commensurate value. Nevertheless, it avoids redundancy and is front-loaded with the core action.

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 zero schema descriptions, no annotations, no output schema, and a tool that interacts with the editor state, the description is insufficient. It lacks parameter documentation, return value description, and explanation of the 'compatibility' designation.

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 'timeoutMs' and 'autoConnect' parameters. The description completely fails to compensate for this gap by explaining what these parameters control, their units, or their operational impact.

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 states a specific action (Open) and resource (scene) with context (in editor), distinguishing it from siblings like 'create_scene' or 'play_scene'. However, the '(Compatibility tool)' parenthetical is opaque and unexplained, preventing a perfect score.

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 guidance on when to use this tool versus alternatives like 'create_scene', 'save_scene', or 'play_scene'. There are no prerequisites or exclusions mentioned.

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