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. It fails to state whether replaying is destructive (modifies game state), blocking (synchronous), or how it handles failures. The 'Compatibility tool' note suggests legacy behavior but doesn't explain what compatibility issues exist or what side effects occur.

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 six words across two sentences. Information is front-loaded with no filler. However, given the complete lack of schema documentation and annotations, this brevity is insufficient rather than efficient—every sentence earns its place, but there aren't enough of them.

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?

Severely incomplete for a complex operation with 0% schema coverage and no output schema. Missing critical context: relationship to start_recording/stop_recording lifecycle, format of acceptable recordings, state side effects, and return behavior. The additionalProperties: true flag in the schema suggests hidden parameters that are entirely undocumented.

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 coverage is 0% with no descriptions for timeoutMs or autoConnect. The description adds no parameter context—e.g., what the timeout applies to (total replay duration? connection timeout?), what autoConnect connects to, or what additionalProperties might contain. It provides only domain context (replay) implying timeout might relate to operation duration.

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 the basic action (replay) and target (recorded input), but 'recorded input' is vague—it doesn't clarify if this refers to recordings from start_recording or macro files. It fails to distinguish from simulate_sequence or other playback siblings, and 'Compatibility tool' raises questions about scope without answering them.

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 parenthetical '(Compatibility tool)' hints at a specific use case but provides no actionable guidance on when to use this versus simulate_sequence or other input methods. No mention of prerequisites (e.g., a recording must exist) or when to prefer alternatives.

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