Godot MCP Bridge

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

With no annotations provided, the description carries full disclosure burden but offers minimal behavioral context. It does not clarify what 'batch' entails (parallel vs sequential), error handling for partial failures, or whether this operation is read-only/safe. The compatibility note lacks behavioral implications.

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 and front-loaded, the description is overly terse for the complexity involved. The two-sentence structure wastes the second sentence on an unexplained parenthetical rather than documenting the parameter scheme or return value.

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 the lack of output schema, 0% parameter coverage, and the 'additionalProperties' pattern requiring documentation, the description is incomplete. It omits return value structure, batch size limits, and the specific input format needed to specify which nodes/properties to fetch.

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 schema has 0% description coverage and uses 'additionalProperties: true', implying arbitrary node/property identifiers should be passed. The description completely fails to explain this critical input contract or what the additional properties represent, leaving the agent unaware of required parameters like node paths or property names.

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 clearly states the core action ('Read') and resource ('multiple node properties in batch'), distinguishing it from single-read siblings like get_node_properties. However, the '(Compatibility tool)' parenthetical is cryptic and unexplained, leaving ambiguity about why/when to prefer this over alternatives.

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 is provided on when to use this tool versus siblings like get_node_properties, get_game_node_properties, or batch_set_property. The 'Compatibility tool' label hints at legacy usage but fails to specify migration paths or deprecation status.

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