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 explain side effects (does this modify project.godot?), persistence, required permissions, or the significance of 'Compatibility tool'. Only the upsert behavior ('Create or update') is implied.

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 and front-loaded, but the '(Compatibility tool)' fragment consumes space without adding actionable context. Given the high complexity implied by 'additionalProperties: true', the description is inappropriately terse rather than efficiently concise.

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 that presumably mutates Godot's InputMap configuration, the description is inadequate. It lacks explanation of the two documented parameters, the open-ended schema, expected return behavior, and interaction with the Godot editor's input system. The absence of an output schema increases the burden on the description, which is not met.

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 and includes 'additionalProperties: true', suggesting arbitrary configuration properties are accepted. The description completely fails to compensate for this, providing no explanation of 'timeoutMs' (timeout for what?), 'autoConnect' (connect to what?), or what additional properties constitute a valid input action configuration.

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 core operation ('Create or update') and resource ('input action'), distinguishing it from the sibling 'get_input_actions'. However, the parenthetical '(Compatibility tool)' is opaque and unexplained, slightly weakening the overall clarity.

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 'get_input_actions' or 'simulate_action'. There is no mention of prerequisites, idempotency considerations, or whether this requires a specific Godot editor state (e.g., project open).

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