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 offers minimal behavioral context. It does not clarify persistence scope, validation rules, error conditions, or the significance of the 'Compatibility' label.

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?

While brief, the cryptic '(Compatibility tool)' tag consumes space without adding usable information. The description is front-loaded but underspecified for the schema 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?

For a mutation tool with zero schema descriptions and a complex additionalProperties pattern, the description is inadequate. It does not explain output behavior, error states, or how to structure the input for multiple settings.

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 has 0% description coverage and uses 'additionalProperties: true' pattern (implying arbitrary setting keys can be passed), but the description mentions only a singular 'value'. It fails to explain that timeoutMs/autoConnect are execution parameters while actual settings use additionalProperties.

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 ('Set') and resource ('project setting'), but the parenthetical '(Compatibility tool)' is unexplained and confusing. It does not differentiate from sibling 'set_' tools (e.g., set_shader_param, set_theme_color) or clarify the relationship to 'get_project_settings'.

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?

No guidance provided on when to use this tool versus alternatives, prerequisites for use, or what 'Compatibility tool' implies (e.g., deprecation, legacy support).

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