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 omits critical behavioral details: it doesn't explain what 'Compatibility tool' implies for behavior, side effects, persistence, or that the tool accepts arbitrary additional properties (additionalProperties: true in schema) which appears to be the primary mechanism for passing parameters.

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 brief (6 words) with no filler. However, it may be overly terse—sacrificing necessary explanatory content for brevity. The core action is front-loaded.

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 annotations, 0% schema coverage, and the complex additionalProperties mechanism, the description is inadequate. It flags the tool as a 'Compatibility tool' but doesn't explain the implications, parameter structure, or expected inputs sufficiently for an agent to invoke it correctly without external knowledge.

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%, yet the description fails to compensate. It doesn't explain the purpose of 'timeoutMs' or 'autoConnect', nor does it clarify that actual AnimationTree parameters must be passed via additionalProperties (arbitrary keys), which is essential given the schema structure.

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 the basic action ('Set AnimationTree parameter') identifying the verb and resource, but the '(Compatibility tool)' label is unexplained jargon. It fails to differentiate from siblings like 'set_blend_tree_node' or 'set_game_node_property'.

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)' vaguely suggests limited or legacy use, but provides no explicit guidance on when to use this versus alternatives, nor does it name the preferred modern replacement.

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