Godot MCP Bridge

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

With zero annotations, the description carries full disclosure burden. While 'raw' hints at output format, it fails to state whether the operation is read-only, safe, or what specific output structure 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?

Extremely efficient with zero fluff; every word conveys meaning. However, the brevity is inappropriate given the complete lack of parameter documentation in the schema.

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 the complexity: two undocumented parameters, no output schema, and no annotations. The description fails to compensate by explaining parameters, return values, or the compatibility 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?

The input schema has 0% description coverage for 'timeoutMs' and 'autoConnect'. The description completely omits these parameters, offering no semantic context for what timeout or auto-connection refers to in this Godot context.

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 specific action (Read) and target resource (raw .tscn content). The '(Compatibility tool)' tag suggests a specialized niche distinct from generic resource readers, though the distinction is not fully explained.

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 tool versus siblings like 'read_resource' or 'get_scene_tree', nor does it explain what 'Compatibility tool' implies for usage scenarios or limitations.

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