Godot MCP Bridge

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

No annotations provided, so description carries full burden. The 'Compatibility tool' note suggests legacy/deprecated behavior but fails to disclose return format, read-only nature, or what specific metadata is retrieved. Critical gap given no output schema exists.

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?

Extremely terse at only 4 words plus a parenthetical. No wasted words or fluff, though brevity comes at the cost of necessary detail. Front-loaded structure with main verb first.

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?

Severely incomplete given zero schema coverage, no output schema, and no annotations. Description fails to explain what metadata is returned or how to interpret results, leaving agents without guidance on successful invocation outcomes.

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 has 0% description coverage for timeoutMs and autoConnect. Description adds zero information about these parameters, failing to compensate for the undocumented schema. No explanation of what the timeout controls or auto-connect behavior.

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 specific verb ('Get') and resource ('tilemap metadata'), distinguishing scope from siblings like tilemap_get_cell (specific cells) and tilemap_get_used_cells (cell lists). The parenthetical '(Compatibility tool)' adds context but remains vague.

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 use versus alternatives like tilemap_get_cell or tilemap_get_used_cells. The 'Compatibility tool' label hints at legacy usage but doesn't explain when this is preferred over other tilemap tools.

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