Godot MCP Bridge

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

No annotations are provided, so the description must carry the full burden. While 'low-level escape hatch' hints at flexibility and potential lack of guardrails, the description fails to disclose critical behavioral traits: whether this blocks on execution, what the return format is, error handling semantics, or whether autoConnect establishes a persistent connection.

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 consists of two highly efficient sentences. The first establishes functionality; the second establishes usage context. Every word earns its place with zero redundancy.

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 tool has 4 parameters, nested objects, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It lacks details on valid command strings, expected return values, or error conditions necessary for an agent to invoke this low-level tool correctly without trial and error.

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, the description must compensate for all four parameters. While 'custom command' loosely maps to the command parameter, it fails to explain the payload structure, timeoutMs behavior, or autoConnect functionality. No examples or valid command formats are provided for the complex nested payload object.

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 clearly states the specific action ('Send a custom command') and target ('Godot bridge'). The phrase 'low-level escape hatch' effectively distinguishes this tool from the 80+ named siblings (add_node, get_scene_tree, etc.) by positioning it as the generic fallback option.

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?

It provides explicit guidance on when to use the tool ('when a named tool is not enough'), implicitly directing users toward the specific sibling tools first. However, it lacks explicit 'when-not-to-use' exclusions or named alternatives that would make the guidance bulletproof.

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