Godot MCP Bridge

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

No annotations exist, so the description carries full burden. It fails to explain what constitutes a 'group' in this context, what the return format is, or what 'Compatibility tool' implies about stability or deprecation. Does not describe the impact of 'autoConnect' or timeout behavior.

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?

Extremely brief (6 words), but underspecified rather than efficiently concise. The '(Compatibility tool)' fragment hints at important context but wastes space by not explaining it. Structure is front-loaded but content-deficient for a tool requiring specific group identification input.

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?

Incomplete for a search tool in a complex node system. No output schema exists, yet the description doesn't explain return values (list of node paths? IDs?). With 'additionalProperties: true' and 0% schema coverage, the description should have documented the primary input parameter, which it omits entirely.

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?

Critical failure: schema has 0% description coverage and 'additionalProperties: true', implying the essential group identifier parameter is undocumented. The description does not compensate by listing required parameters (e.g., group name) or explaining 'timeoutMs'/'autoConnect' semantics. User cannot invoke this tool successfully from documentation alone.

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?

States the basic action (find nodes) and target (group), but 'group' is Godot-specific jargon without explanation. Fails to differentiate from sibling 'get_node_groups' (which retrieves groups, not nodes). The '(Compatibility tool)' parenthetical is opaque and hints at legacy behavior without clarifying.

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?

Provides no guidance on when to use this versus 'get_node_groups', 'find_nodes_by_type', or 'find_node_references'. Does not explain the implications of 'Compatibility tool' (e.g., whether a newer alternative exists). No prerequisites or scoping guidance provided.

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