Godot MCP Bridge

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides none. It does not explain what inputs are compared (file paths, buffers, current screen?), what the comparison methodology is, what the return value or output format is, or what the side effects might be.

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?

While extremely brief (two fragments), the description sacrifices essential information for brevity. The '(Compatibility tool)' parenthetical consumes space without conveying actionable meaning, and the front-loaded verb fails to establish context for the parameters or return value.

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?

Completely inadequate for a 2-parameter tool with no output schema and no annotations. Critical missing information includes: the source of screenshots being compared, the comparison algorithm, success/failure criteria, and the meaning of the 'compatibility' designation.

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?

The input schema has 0% description coverage for its two parameters (timeoutMs, autoConnect), and the description adds no clarification. It is unclear what timeoutMs refers to (comparison duration? connection timeout?) or what autoConnect connects to, leaving the parameters effectively undocumented.

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 merely restates the tool name with a verb ('Compare screenshots'), constituting a near-tautology. The parenthetical '(Compatibility tool)' is cryptic and unexplained, failing to clarify what kind of comparison is performed (pixel diff, perceptual, etc.) or distinguish from sibling screenshot tools like get_game_screenshot.

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?

No guidance provided on when to use this tool versus alternatives like assert_screen_text or manual inspection. The cryptic 'Compatibility tool' label hints at potential deprecation or backward compatibility usage, but fails to explain what the modern alternative might be or when this specific tool is appropriate.

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