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 burden. It fails to disclose that the tool accepts arbitrary additional properties (additionalProperties: true), does not explain the connection behavior implied by 'autoConnect' and 'timeoutMs' parameters, and omits what format or structure the resource properties return in.

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 extremely brief at two short sentences. While not verbose, it is insufficiently informative for a tool with zero schema documentation and no annotations; the brevity reflects under-specification rather than efficient information density.

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 the lack of output schema, annotations, and parameter descriptions, the description should explain the return value, connection behavior, and scope of 'resource properties.' It provides none of this, leaving critical gaps in the agent's understanding of how to invoke the tool or what to expect from it.

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?

With 0% schema description coverage, the description must compensate but does not mention either parameter. While 'timeoutMs' and 'autoConnect' names are somewhat self-explanatory, the description adds no context about what connection timeout or auto-connection refers to in this resource-reading context, nor does it document the additionalProperties capability.

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 a clear verb ('Read') and target ('resource properties'), which aligns with the tool name. However, it fails to distinguish from siblings like 'get_resource_preview' or 'edit_resource' (which may also read), and the '(Compatibility tool)' note lacks explanation of what compatibility means or which alternative to use instead.

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 only usage hint is the parenthetical '(Compatibility tool)', implying legacy or fallback usage, but it provides no explicit guidance on when to prefer this over 'edit_resource', 'create_resource', or 'get_resource_preview', nor does it explain the compatibility scenario or prerequisites.

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