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 disclosure burden, yet it reveals nothing about the return format (base64 image? file path?), error handling, side effects (does it generate thumbnails or only retrieve cached ones?), or what 'compatibility' refers to (Godot 3.x vs 4.x?).

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 at six words plus a parenthetical. While not verbose, the brevity constitutes under-specification rather than efficient communication—the '(Compatibility tool)' aside consumes space without conveying useful behavioral context, and critical parameter information is omitted entirely.

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, the description should explain the return format (likely image data). With undocumented parameters and no annotations, the description leaves critical gaps: it doesn't specify the resource identification mechanism, return type, or the 'compatibility' context, making it insufficient for safe invocation.

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 for the two defined parameters ('timeoutMs' and 'autoConnect') and 'additionalProperties: true' suggesting a resource identifier is required, the description completely fails to document what parameters are expected, their semantics, or what resource identifier format is required.

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 the basic action ('Get resource preview thumbnail') with a clear verb and object, but the '(Compatibility tool)' parenthetical is cryptic and unexplained. It fails to distinguish from sibling tools like 'read_resource' or clarify what constitutes a 'resource' in this context.

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 explicit guidance on when to use this tool versus 'read_resource' or 'get_editor_screenshot'. The '(Compatibility tool)' note implies legacy usage but fails to specify what modern alternative should be used instead, leaving the agent without actionable selection criteria.

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