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 only offers the cryptic '(Compatibility tool)' hint without explaining side effects, idempotency, whether it modifies the scene file immediately, or what the 'Compatibility' designation implies for behavior (legacy support?).

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 text is front-loaded and efficient with words, but given the 0% schema coverage and lack of annotations, it is inappropriately terse for the domain complexity. It sacrifices necessary detail for brevity, resembling underspecification rather than effective conciseness.

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?

Inadequate for a Godot animation tool with undocumented parameters and no output schema. The description omits critical context such as state naming conventions, positioning within the state machine graph, relationships to transitions, and the meaning of 'Compatibility tool' in the Godot 4.x context.

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 adds zero information about the two parameters ('timeoutMs' and 'autoConnect'). It fails to explain what the timeout applies to or what automatic connection occurs, leaving the agent to guess parameter semantics entirely.

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?

States a specific action ('Add') and target resource ('AnimationTree state machine state'), clearly positioning it within the Godot animation domain. Distinguishes from generic 'add_node' and transition-related siblings by specifying 'state', though it doesn't elaborate on what constitutes a 'state' 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?

Provides no guidance on when to use this tool versus alternatives like 'create_animation_tree' or 'add_state_machine_transition'. Does not mention prerequisites (e.g., requiring an existing AnimationTree node) or when to prefer this over removing states. The '(Compatibility tool)' tag is unexplained.

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