Godot MCP Bridge

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states nothing about side effects (does it modify the scene? create nodes?), return values, idempotency, or the implications of the 'Compatibility' label. The agent cannot determine if this is a safe operation or what state changes to expect.

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 (6 words), which technically wastes no words, but it is 'too concise' to the point of being uninformative. The cryptic parenthetical '(Compatibility tool)' consumes space without adding clarity. Every sentence should earn its place; here, neither sentence earns sufficient value.

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 'setup' tool with 2 parameters and no output schema, the description is woefully inadequate. It omits what gets set up (existing node vs new node), the relationship between the parameters and the resulting behavior, and any Godot-specific context (e.g., NavigationAgent3D vs NavigationAgent2D). The description provides no more information than the function name itself.

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% (timeoutMs and autoConnect are undocumented in the schema), yet the description provides no compensation. It fails to explain what the timeout applies to, what autoConnect connects to, or what additional properties (additionalProperties: true) might be accepted.

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 restates the tool name with spaces added ('Set up navigation agent'), which is tautological. It adds '(Compatibility tool)' without explanation, leaving the actual purpose ambiguous—does it create, configure, or initialize a navigation agent? It fails to distinguish from sibling tool setup_navigation_region.

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 (e.g., setup_navigation_region), prerequisites for use, or when it should be avoided. The parenthetical '(Compatibility tool)' is unexplained jargon that could imply deprecation or legacy usage, but offers no actionable guidance.

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