Godot MCP Bridge

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to explain execution time characteristics (despite timeoutMs parameter suggesting potential hangs), side effects, or what the 'compatibility' designation implies for behavior. The cryptic parenthetical adds no actionable behavioral context.

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?

Brief and front-loaded with the primary verb, but the '(Compatibility tool)' parenthetical wastes space without explanation. Every sentence should earn its place; this adds an unexplained categorization that confuses rather than clarifies.

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 annotation coverage, no output schema, and 0% parameter documentation, the description is grossly insufficient. For a complex analytical operation in a Godot environment, it lacks essential context: return value structure, specific metrics analyzed, and error conditions.

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?

With 0% schema description coverage, the description must compensate for undocumented parameters (timeoutMs, autoConnect) but completely fails to do so. No explanation of what connection autoConnect establishes or why a timeout might be necessary.

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?

States the core action ('Analyze') and target ('scene complexity metrics'), but 'complexity metrics' remains vague regarding what specific metrics are computed. The parenthetical '(Compatibility tool)' is cryptic and doesn't clarify scope or differentiate from sibling analysis tools like analyze_signal_flow or run_stress_test.

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?

Provides no guidance on when to prefer this over alternatives like run_stress_test or get_scene_dependencies, nor does it explain the significance of it being a 'compatibility tool' (deprecated? legacy?). Lacks prerequisites or constraints for invocation.

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