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 disclosure burden. While it mentions '(Compatibility tool),' this behavioral hint is unexplained and therefore not actionable. The description does not clarify what 'details' are returned, potential side effects, or why connection-related parameters (`autoConnect`) are present for a getter operation.

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 at only two clauses. However, the second clause '(Compatibility tool)' wastes space by introducing ambiguity without explanation, preventing a perfect score despite the brevity.

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?

Given the lack of annotations, output schema, and zero schema parameter descriptions, the description is insufficient. It fails to define what constitutes an 'autoload node' in this context (Godot engine singletons) or what data structure the agent should expect from the operation.

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?

With 0% schema description coverage for both `timeoutMs` and `autoConnect`, the description needed to compensate by explaining these parameters. It mentions neither, leaving the agent without information about units (milliseconds), valid ranges, or the relationship between connection parameters and retrieving autoload data.

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 basic action ('Get') and resource ('autoload node details'), providing minimal clarity. However, the parenthetical '(Compatibility tool)' is undefined and confusing, and the description fails to explain what distinguishes this from sibling tools like `add_autoload` or `remove_autoload` beyond the obvious verb difference.

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 description provides no guidance on when to use this tool versus alternatives such as `get_node_properties` or `get_scene_tree`. It does not explain the significance of the 'Compatibility tool' label (e.g., whether this is deprecated) or prerequisites for invocation.

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