Godot MCP Bridge

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only hints at behavior with '(Compatibility tool)' but does not explain side effects, what happens to existing particle configurations when a preset is applied, or the implications of the 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 (5 words plus a parenthetical), which technically avoids verbosity, but given the complete lack of schema documentation and annotations, this brevity constitutes under-specification rather than effective conciseness. The 'compatibility' note is underexplained.

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?

The tool lacks an output schema, annotations, and parameter descriptions. The description does not explain return values, error conditions, or how this operation interacts with the Godot particle system. For a tool manipulating complex scene elements with two undocumented parameters, this is inadequate.

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 both 'timeoutMs' and 'autoConnect' parameters. The description fails to compensate by explaining what these parameters control, what the timeout applies to, or what auto-connection establishes. This leaves critical operational parameters 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?

The description states the basic action ('Apply particle effect preset') but fails to define what constitutes a 'preset' in this context. The parenthetical '(Compatibility tool)' is ambiguous—it is unclear whether this indicates the tool is legacy/deprecated or applies compatibility-specific presets, creating confusion rather than clarity.

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 sibling alternatives like 'create_particles', 'set_particle_material', or 'set_particle_color_gradient'. It does not mention prerequisites, such as whether a particle node must exist beforehand, or when the compatibility mode is necessary.

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