Godot MCP Bridge

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

With no annotations provided, the description carries full burden but discloses almost nothing about side effects (does this write files to disk?), safety (is it destructive?), or execution model (blocking vs async). The dual 'get' vs 'trigger' behavior is mentioned but not explained, leaving critical behavioral gaps.

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 phrases. While efficient in word economy, the conciseness crosses into under-specification given the tool's complexity and lack of supporting schema documentation.

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?

For a tool likely performing project exports (potentially long-running, file-writing operations), the description lacks essential details: return value format (command string? status object?), export output location, and the significance of the 'Compatibility tool' designation. No output schema exists to compensate.

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%, leaving 'timeoutMs' and 'autoConnect' undocumented in the structured fields. The description adds no context for these parameters—particularly 'autoConnect' (connect to what?)—and fails to explain how they influence the ambiguous 'get' versus 'trigger' behavior.

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 identifies the domain (export) and mentions two possible actions: 'Get export command' or 'trigger export'. However, it fails to clarify whether these are distinct modes, conditional behaviors, or synonymous actions, creating ambiguity about the tool's actual function.

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 is provided on when to use this tool versus siblings like 'get_export_info' or 'list_export_presets'. The parenthetical '(Compatibility tool)' hints at legacy status but fails to specify what should be used instead or under what circumstances this tool remains appropriate.

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