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 only the cryptic note '(Compatibility tool)' without explaining what compatibility means, what side effects occur, or what the timeoutMs parameter controls. Mutation potential is implied by 'set up' but not explicit.

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 (two fragments) but this represents under-specification rather than efficient communication. The '(Compatibility tool)' parenthetical is under-explained and wastes potential space for actual behavioral description.

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 Godot navigation tool with 2 parameters and implied node creation/configuration behavior, the description is inadequate. It fails to explain the relationship between navigation regions and navigation meshes, the role of the parameters, or expected outcomes.

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 description coverage is 0% and the description completely fails to compensate. Neither timeoutMs (timeout for what operation?) nor autoConnect (connect to what?) are explained, leaving critical parameters undocumented.

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 up navigation region' is a tautology that restates the tool name with minimal elaboration. While it identifies the resource (navigation region), it fails to specify what 'set up' entails (creation, configuration, initialization) or distinguish from siblings like bake_navigation_mesh or setup_navigation_agent.

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 such as bake_navigation_mesh, setup_navigation_agent, or set_navigation_layers. No prerequisites mentioned (e.g., requiring an existing scene or specific node type).

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