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 only adds the 'Compatibility tool' context. It omits whether this creates, references, or modifies resources, what happens to existing attachments, side effects, or operational constraints.

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 plus parenthetical) and front-loaded with the action, but its brevity constitutes under-specification rather than efficient communication given the tool's complexity.

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?

Inadequate for a tool with flexible schema (`additionalProperties`) and no output schema. The description misses critical context about expected inputs, return behavior, and the Godot-specific meaning of 'attach' in this context.

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% for both `timeoutMs` and `autoConnect`, and the description fails to compensate by explaining these parameters or the critical `additionalProperties: true` pattern (what extra properties are expected?).

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 states the core action ('Attach resource to node') with a specific verb and resource type, but fails to differentiate from siblings like `create_resource`, `read_resource`, or `edit_resource`, leaving ambiguity about when attachment is preferred over creation or modification.

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)' weakly implies legacy usage but provides no explicit when-to-use guidance, no named alternatives, and no prerequisites (e.g., whether the node or resource must exist first).

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