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 disclosure burden. It fails to specify what data format is returned, what constitutes a 'cell' in this context, error behaviors, or why this is marked as a compatibility tool. Minimal behavioral context provided.

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 brief (4 words plus parenthetical) and front-loaded, but inappropriately sized for the complexity. With zero schema documentation and no annotations, the description needs substantially more detail to be functional; brevity here represents under-specification rather than efficient communication.

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?

Inadequate for a getter tool with no output schema and 0% parameter documentation. Missing: cell identification method (coordinates), return value structure, tilemap targeting mechanism, and explanation of the 'compatibility' designation. Does not meet the minimum viable threshold for agent invocation confidence.

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% (timeoutMs and autoConnect undocumented). The description does not compensate by explaining these parameters or the implied cell coordinates (x, y) likely needed given the function name. With additionalProperties: true in schema, critical parameter semantics are completely missing.

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 basic operation ('Get tile cell data') with specific verb and resource, but fails to differentiate from siblings like 'tilemap_get_used_cells' or 'tilemap_get_info'. The parenthetical '(Compatibility tool)' is cryptic and unexplained, leaving ambiguity about whether this is deprecated or legacy functionality.

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 this tool versus the four other tilemap-related tools (tilemap_get_info, tilemap_get_used_cells, etc.). Does not explain what 'compatibility tool' implies for usage patterns or prerequisites.

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