Godot MCP Bridge

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

No annotations are provided, so the description carries the full burden. It implies a batch operation affects multiple targets, but does not disclose whether operations are atomic, what happens if the filter matches zero nodes, or what the return value indicates.

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 concise (six words), which is efficient but underspecified for a complex batch operation tool. The parenthetical note earns no clarity. Front-loaded structure is good, but content is insufficient.

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?

Severely incomplete given the tool's apparent complexity (batch mutations with flexible filtering via additionalProperties). No output schema, no parameter documentation, and no explanation of filter syntax or available property types leaves critical gaps.

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 fails to compensate. It mentions 'filter' but the schema shows no filter parameter (only 'timeoutMs' and 'autoConnect'), and does not explain that 'additionalProperties' likely contains the filter criteria and property values to set.

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 core action (batch set property) and mechanism (by filter), but lacks domain context (Godot nodes) and the parenthetical '(Compatibility tool)' is cryptic without explanation of what compatibility is being maintained.

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 versus siblings like 'set_game_node_property', 'update_property', or 'cross_scene_set_property'. Does not clarify what constitutes a 'batch' scenario or when filtering is preferred over direct reference.

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