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 no behavioral traits. It mentions 'compatibility' without explaining the implications (e.g., deprecated features, specific version requirements), and fails to state side effects, idempotency, or what 'setting up' actually entails (e.g., creating default lights vs. configuring existing ones).

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 with no redundant words or filler. However, this conciseness crosses into under-specification—every word earns its place, but there are too few words to adequately describe the tool's function.

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 lack of schema descriptions, annotations, and output schema, the description is insufficient for an agent to use the tool correctly. It omits critical context about the parameters, the 'compatibility' nature of the tool, and expected outcomes of the setup operation.

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 schema has 0% description coverage for its two parameters (timeoutMs and autoConnect), and the description fails to compensate by explaining what the timeout applies to (operation duration? light fade?) or what autoConnect connects to. The agent has no textual guidance for interpreting these parameters.

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 resource (lighting nodes) and hints at the domain (compatibility), but uses the vague verb 'set up' without clarifying whether it creates, configures, or initializes nodes. It distinguishes from siblings by the 'compatibility' label but doesn't explain what makes this different from generic node addition tools like add_node.

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)' implies this may be a legacy or secondary method, but provides no explicit guidance on when to prefer this over alternatives like add_node, nor does it state prerequisites for the lighting setup. No exclusions or prerequisites are mentioned.

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