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 disclosure burden. The 'Compatibility tool' note hints at behavioral traits (possibly deprecated or legacy) but is too vague to be actionable. It fails to disclose what additional properties are accepted (despite additionalProperties: true), error conditions, or mutation scope.

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 at one sentence plus a parenthetical. While not verbose, the '(Compatibility tool)' remark wastes space by being unexplained, and the front-loading doesn't prioritize the most critical information (the missing parameter 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?

Given this is a mutation tool with no annotations, no output schema, and zero schema coverage, the description is grossly incomplete. It omits the expected gradient parameter format, the meaning of 'compatibility,' and how it integrates with the particle system workflow.

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, the description needed to compensate for timeoutMs and autoConnect, plus explain what gradient data structure is expected via additionalProperties. It adds zero parameter semantics, leaving all inputs undocumented.

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 ('Set') and target ('particle color gradient'), but the '(Compatibility tool)' parenthetical is cryptic and unexplained. It does not clarify how this differs from sibling tools like set_particle_material or apply_particle_preset, leaving ambiguity about which particle tool to use.

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 (e.g., set_particle_material), nor prerequisites such as requiring an existing particle system. No 'when-not-to-use' or workflow context is provided.

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