Godot MCP Bridge

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

With no annotations provided, the description carries full disclosure burden but offers almost nothing. Fails to explain what happens to game state/nodes during stop, whether the operation is graceful or forceful, or what conditions might cause failure. No mention of return behavior.

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 brief (5 words), which is efficient but to a fault. The parenthetical '(Compatibility tool)' wastes space without clarifying compatibility with what, or why it matters. Front-loaded but uninformative.

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 zero schema descriptions, no annotations, no output schema, and a significant side-effect operation (terminating a running scene), the description is inadequate. It does not prepare the agent to use the tool safely or understand its parameter implications.

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 has 0% description coverage (timeoutMs and autoConnect are undocumented). The description completely fails to compensate—it mentions neither parameter nor their semantics. 'timeoutMs' and 'autoConnect' are cryptic without explanation (timeout for what? connect to what?).

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?

States the basic action (stop) and target (running scene) clearly. Distinguishes from sibling 'play_scene' implicitly. However, the parenthetical '(Compatibility tool)' is vague and unexplained, leaving ambiguity about why/when to prefer this over alternatives.

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., scene must be actively running), or side effects. No mention of the relationship to 'play_scene' or scene lifecycle management.

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