Godot MCP Bridge

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

With no annotations provided, the description carries full disclosure burden but reveals nothing about side effects, persistence (where the animation is saved), return values, or what 'Compatibility tool' implies regarding behavior differences from standard creation methods.

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 two-sentence structure is efficient with no redundant text; every word attempts to convey meaning. However, the extreme brevity contributes to underspecification rather than optimal information density.

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 state-mutating creation tool with undocumented parameters and no output schema, the description is insufficient. It lacks essential context about the Godot Animation resource lifecycle, prerequisite nodes (AnimationPlayer), or integration with sibling tools.

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% and the description completely fails to compensate. Critical parameters 'timeoutMs' and 'autoConnect' are undocumented—the agent cannot infer what timeout applies to or what auto-connects to what without external knowledge.

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 ('Create new animation') but provides minimal differentiation from siblings like 'create_animation_tree' or 'add_animation_track'. The parenthetical '(Compatibility tool)' is opaque and doesn't clarify scope or resource type created.

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 explicit guidance on when to use versus alternatives (e.g., 'add_animation_track' for modifying existing animations). The 'Compatibility tool' notation hints at a specific use case but fails to explain what compatibility concerns or prerequisites apply.

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