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 but provides none. It does not explain what an animation track is, prerequisites (e.g., requiring an existing animation), side effects, return values, or what 'compatibility' implies for behavior.

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 (4 words), it is under-specified rather than efficiently concise. The '(Compatibility tool)' tag consumes space without providing actionable information. Every sentence should earn its place; this description fails to establish context or parameters.

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 interacting with animation systems (implied by siblings like create_animation, get_animation_info), the description is inadequate. With 2 undocumented parameters, no output schema, no annotations, and no explanation of animation track concepts, the description provides insufficient context for correct invocation.

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 input schema has 0% description coverage for its two parameters (timeoutMs, autoConnect). The description fails to compensate by explaining what timeoutMs measures (connection timeout? animation duration?), what autoConnect connects to, or why these parameters exist for an animation track tool.

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 ('Add animation track') but provides minimal context. It does not distinguish this tool from siblings like 'create_animation' or 'set_animation_keyframe', leaving ambiguity about whether this creates a new animation or adds a track to an existing one.

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 provided on when to use this tool versus alternatives. The parenthetical '(Compatibility tool)' is cryptic and unexplained—if this indicates deprecation or legacy status, it should specify the preferred alternative, which it does not.

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