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 almost none. It does not explain where recordings are stored (memory, filesystem, or output), whether the operation blocks, what happens upon timeout, or the implications of the 'compatibility' designation.

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 the description is brief at only four words plus a parenthetical, the brevity reflects under-specification rather than efficient information density. The cryptic '(Compatibility tool)' annotation consumes space without adding actionable meaning or context.

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 stateful nature of recording operations, the lack of output schema, zero parameter documentation, and no explanation of the recording lifecycle (start/stop/replay), the description is inadequate. It omits essential context about recording duration limits, storage mechanisms, and session management.

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 both timeoutMs and autoConnect, and the description fails to compensate by explaining these parameters. No information is provided about the timeout duration behavior, units, or what 'autoConnect' connects to, leaving critical operational parameters completely 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 states the basic action ('Start input recording') with a clear verb and resource, distinguishing it from sibling stop_recording. However, 'input recording' lacks specificity regarding input type (keyboard, mouse, gamepad) and the parenthetical '(Compatibility tool)' is cryptic and unexplained.

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 regarding when to use this tool versus alternatives like simulate_sequence, or that it must be paired with stop_recording to complete a capture session. The description lacks any mention of prerequisites or sequencing requirements.

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