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 fails to mention whether the operation is destructive, idempotent, or what happens if the Camera3D node does not exist. The 'Compatibility tool' note is the only behavioral hint, but lacks explanation of its 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?

The description is extremely concise with only two short statements. It is front-loaded with the primary action and the parenthetical compatibility note adds distinct context without verbosity. However, given the lack of schema documentation, it may be overly terse.

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 zero schema coverage, no output schema, and no annotations, the description is insufficient for a tool accepting arbitrary properties via `additionalProperties`. It fails to specify which Camera3D properties are supported, expected formats, or the return behavior, leaving critical gaps in contextual information.

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?

Schema description coverage is 0%, requiring the description to compensate. While 'Set Camera3D properties' implies that arbitrary camera properties can be passed (aligning with `additionalProperties: true`), the description completely omits the purpose of the explicitly defined parameters `timeoutMs` and `autoConnect`, leaving their semantics 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 a clear action ('Set') and resource ('Camera3D properties'), making the basic purpose understandable. However, while the '(Compatibility tool)' note hints at differentiation from siblings like `set_game_node_property`, it fails to explain exactly how this tool differs or what 'compatibility' implies in this context.

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 alternatives such as `set_game_node_property` or `batch_set_property`. The 'Compatibility tool' parenthetical implies a specific use case but does not clarify prerequisites, deprecation status, or when to avoid using it.

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