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. It only adds the 'Compatibility tool' notation, which hints at deprecation or legacy behavior, but fails to explain mutation scope, required permissions, error conditions, or what happens to existing anchor settings.

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 brief and front-loaded, but inappropriately terse given the complete lack of schema documentation. The '(Compatibility tool)' aside is useful but cryptic; the description wastes no words yet fails to earn its keep by omitting critical parameter 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?

For a mutation tool with undocumented parameters and no output schema, the description is incomplete. It omits available preset values, Control node prerequisites, the meaning of 'Compatibility tool,' and return value information necessary for safe invocation.

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 its two parameters ('timeoutMs' and 'autoConnect'), yet the description provides no compensation—failing to explain what values are expected for anchor presets, parameter relationships, or why connection-related parameters exist on an anchor tool.

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 identifies the action ('Set'), resource ('anchor preset'), and target ('Control node'), distinguishing it from generic property setters like 'set_game_node_property' or 'set_node_groups' in the sibling list. However, it assumes familiarity with Godot's Control node system without briefly explaining what anchor presets accomplish.

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 '(Compatibility tool)' parenthetical implies legacy usage but provides no explicit guidance on when to use this versus 'set_game_node_property' or other node manipulation tools. No prerequisites, exclusions, or alternative approaches are documented.

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