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 disclosure burden but fails to explain what 'Compatibility tool' implies (legacy status? limited functionality?), what the simulation entails (instant teleport vs. smooth traversal), or why the parameters are connection-oriented (timeoutMs, autoConnect) rather than positional.

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 at only four words plus a parenthetical, the description suffers from under-specification rather than efficient precision. The '(Compatibility tool)' tag consumes space without conveying actionable meaning, and critical information (parameter purposes, coordinate handling) is entirely absent.

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 mouse simulation tool with 'additionalProperties: true' in the schema, the description omits crucial details: how to specify target coordinates (or if they're required), what happens after the timeout expires, and the expected side effects. Without an output schema or annotations, the description needed to compensate but did not.

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 input schema has 0% description coverage, yet the description provides no semantic information about 'timeoutMs' (timeout for what operation?) or 'autoConnect' (connect to what?). It also fails to explain the mismatch between the tool's purpose (mouse movement) and the absence of coordinate parameters, leaving the agent uncertain how to specify the movement destination.

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 the basic action ('Simulate mouse movement') but is essentially a restatement of the tool name. The '(Compatibility tool)' parenthetical is cryptic and unexplained, failing to clarify scope or distinguish this from the sibling 'simulate_mouse_click' tool beyond the obvious 'movement' vs 'click' distinction.

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 alternatives like 'simulate_mouse_click', 'simulate_action', or 'simulate_sequence'. Given the unusual parameter schema (lacking coordinate inputs), the absence of prerequisites or usage context is a significant gap.

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