Godot MCP Bridge

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

No annotations are provided, so the description carries the full burden. It adds the 'Compatibility tool' behavioral context but fails to disclose error conditions, return value format, side effects, or whether this requires an active connection.

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 concise at two brief clauses with zero redundant words. Every element earns its place.

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 description coverage, no output schema, and unexplained input mechanism, the description is insufficient. It should elaborate on how to provide the UID and what the tool returns.

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%. The description completely fails to explain the two parameters (timeoutMs, autoConnect) or clarify how the UID input is provided—critical given the schema defines no UID field and relies on additionalProperties.

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 function with specific verb and resource ('Convert UID to res:// project path'). The parenthetical '(Compatibility tool)' adds scope context. It implicitly distinguishes from sibling 'project_path_to_uid' via directionality, though it does not explicitly name the inverse tool.

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?

The '(Compatibility tool)' label implies a specific usage context (likely legacy or transition scenarios), but provides no explicit guidance on when to prefer this over alternatives, prerequisites, or when NOT to use it.

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