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. 'Edit' implies mutation but the description doesn't clarify if this is destructive, what happens to unspecified properties, or why connection-related parameters (timeoutMs, autoConnect) are present. The 'Compatibility tool' note suggests special behavior but remains unexplained.

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 brief (4 words plus parenthetical), but given the complexity (additionalProperties: true, 0% schema coverage, unclear parameter mapping), it is insufficiently informative rather than appropriately concise.

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?

Inadequate for the tool's complexity. With dynamic parameters via additionalProperties, no output schema, and numerous sibling tools suggesting a complex domain (Godot engine), the description should explain the parameter passing pattern, return values, and compatibility implications.

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 doesn't explain that actual resource properties likely pass through additionalProperties, nor does it clarify the purpose of timeoutMs and autoConnect (which appear to be connection parameters rather than resource editing parameters).

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 ('Edit resource properties') but remains generic. While 'Compatibility tool' provides some distinction, it fails to differentiate from siblings like update_property, batch_set_property, or create_resource regarding specific use cases or scope.

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., update_property for single values, batch_set_property for multiple, or read_resource for inspection). The '(Compatibility tool)' label hints at legacy usage but offers no explicit when-to-use or when-not-to-use criteria.

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