Godot MCP Bridge

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

With no annotations provided, the description carries full burden but discloses minimal behavioral traits. While 'over time' suggests polling/continuous observation, it fails to explain the blocking nature (implied by timeoutMs), return format, what autoConnect connects to, or the implications of additionalProperties: true (likely property name arguments).

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 concise at only 7 words plus a tag. Every element carries information, and it is front-loaded with the action. However, the '(Compatibility tool)' parenthetical is structurally awkward and lacks context, preventing a perfect score.

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?

For a tool with zero schema descriptions, no output schema, and dynamic parameter acceptance (additionalProperties: true), the description is insufficient. It omits critical context such as the monitoring mechanism, expected return data, the meaning of the compatibility warning, and how to specify which properties to monitor.

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?

Given 0% schema description coverage, the description must compensate but adds nothing. It fails to explain that timeoutMs controls monitoring duration, what autoConnect connects to, or what additional properties (property names to watch?) should be passed via additionalProperties: true.

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 a clear action (monitor) and target (property values over time), but lacks specificity about what kind of properties (node, game, editor?) and fails to distinguish from siblings like batch_get_properties or get_node_properties. The '(Compatibility tool)' tag is cryptic and unexplained.

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 parenthetical '(Compatibility tool)' implies deprecation or legacy status, suggesting caution, but provides no explicit guidance on when to use this versus alternatives like batch_get_properties, nor does it name a preferred replacement. No when-not-to-use scenarios are described.

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