Godot MCP Bridge

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

No annotations are provided, so the description carries full burden. It fails to disclose side effects (does this modify a file or session state?), persistence of the 'override,' or explain why this is marked as a compatibility tool. The timeoutMs and autoConnect parameters in the schema suggest connection behavior that is not addressed.

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 (two fragments), which would be acceptable if information-dense, but the '(Compatibility tool)' aside wastes space without explanation. The front-loading is adequate but the severe underspecification given the schema complexity makes the brevity problematic rather than efficient.

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?

With zero schema coverage, no annotations, and no output schema, the description provides critically insufficient context. It does not explain the expected input format for font sizes, the role of the timeout/autoConnect parameters, or what the 'override' applies to. The mismatch between description text and schema structure leaves the agent without viable usage instructions.

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% and the description completely fails to compensate. There is a severe disconnect between the stated purpose (setting font size) and the actual schema parameters (timeoutMs, autoConnect). With additionalProperties: true, the description must specify what properties to pass for the font size operation, but it provides no parameter guidance whatsoever.

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 specific action (Set) and resource (theme font size override), but the '(Compatibility tool)' parenthetical is cryptic and unexplained. It does not clarify the scope (which theme?) or distinguish from siblings like set_theme_constant.

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 alternatives such as set_theme_constant or create_theme. The '(Compatibility tool)' note hints at a specific use case but fails to explicitly state when this should be preferred or avoided.

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