Godot MCP Bridge

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

No annotations are provided, so the description carries full disclosure burden. It fails to explain side effects, idempotency, what happens to existing groups, or what 'Compatibility tool' implies regarding legacy behavior or limitations.

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 brief, the description is under-specified rather than efficiently concise. The single sentence provides almost no actionable information beyond the tool name, wasting the opportunity to front-load critical usage constraints.

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?

Completely inadequate for a tool with 0% schema coverage and no annotations. The description fails to explain the input model (how groups are specified), the output, or the 'compatibility' nature, leaving the agent with no operational guidance.

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 but provides no parameter details. It does not explain why timeoutMs and autoConnect exist for a group-setting operation, nor does it document the additionalProperties pattern which likely carries the actual group data.

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 'Set node groups' restates the tool name (tautology). The parenthetical '(Compatibility tool)' adds minimal context but fails to explain what node groups are, what 'setting' them entails, or how this differs from sibling get_node_groups.

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 provided on when to use this tool versus alternatives, prerequisites (e.g., requiring an active node or scene), or why it is marked as a 'compatibility' tool. The agent has no information to determine appropriate invocation context.

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