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 but offers minimal behavioral context. It does not explain what happens if the button isn't found, what the tool returns, or why this is labeled a 'Compatibility tool'. The presence of a 'timeoutMs' parameter suggests waiting behavior that should have been described.

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 appropriately brief at two fragments, but the '(Compatibility tool)' parenthetical wastes limited space without adding actionable information. The core action is front-loaded, which is good, but the overall length is too minimal given the lack of schema documentation.

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 unclear parameter requirements (implied 'text' parameter missing from schema), the description is severely incomplete. For a UI automation tool, it should describe error handling, search scope, and the 'compatibility' context.

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%, yet the description fails to compensate by explaining either 'timeoutMs' (likely wait duration) or 'autoConnect' (unclear what it connects to). Critically, the tool name implies a text content parameter is required, but with 'additionalProperties: true' in the schema, the description must clarify what additional properties are expected, which it does not.

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 action ('Click button') and the selection mechanism ('by text content'), which distinguishes it from coordinate-based siblings like 'simulate_mouse_click'. However, the parenthetical '(Compatibility tool)' is cryptic and doesn't clarify what compatibility is being maintained.

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 'find_ui_elements'. The 'Compatibility tool' label hints at legacy usage but fails to specify preferred modern alternatives or prerequisites.

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