Godot MCP Bridge

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

No annotations are provided, yet the description discloses no behavioral traits. It does not explain the 'compatibility' nature, side effects of adding transitions, or the significance of additionalProperties: true allowing arbitrary extra parameters.

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, the description is under-specified rather than efficiently concise. The parenthetical '(Compatibility tool)' consumes space without earning its place—it provides a label without explanation or actionable context.

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 the flexible schema (additionalProperties: true), unexplained parameter names, and lack of output schema or annotations, the description is woefully incomplete. An agent would be unable to invoke this tool correctly without significant external knowledge.

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 mention timeoutMs or autoConnect, nor explain why connection-oriented parameters exist on a state machine tool, leaving the agent unable to infer valid inputs.

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 tautologically restates the tool name ('Add state machine transition') with only the cryptic parenthetical '(Compatibility tool)' added. It fails to distinguish from sibling tools like add_state_machine_state or explain what distinguishes a 'compatibility' transition.

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 (e.g., add_state_machine_state), nor what 'Compatibility tool' implies for usage patterns. The agent cannot determine prerequisites or deprecation status.

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