Godot MCP Bridge

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

No annotations are provided, so the description must carry the full burden of disclosing behavior. It fails to indicate whether this is a destructive operation, what happens to connected states when a transition is removed, or whether the change is immediate/reversible. The agent must infer mutation risk solely from the verb 'Remove'.

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 brief (one sentence fragment), but the '(Compatibility tool)' annotation wastes space without explanation. While not verbose, the extreme brevity crosses into under-specification, failing to front-load critical context about the operation's scope 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?

Given this is a destructive mutation tool on state machine resources with no output schema, no annotations, and undocumented parameters, the description is critically incomplete. It lacks necessary context about side effects, return behavior, or the meaning of its generic-looking parameters.

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?

With 0% schema description coverage for the 'timeoutMs' and 'autoConnect' parameters, the description completely fails to compensate. It does not explain what these parameters control (e.g., connection timeout vs. state machine timeout), why they exist for a transition removal operation, or how they affect the tool's execution.

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 verb and resource ('Remove state machine transition'), but it is essentially a restatement of the tool name with minimal elaboration. The '(Compatibility tool)' parenthetical adds no actionable clarity and does not differentiate from sibling tools like 'remove_state_machine_state' or 'add_state_machine_transition'.

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 is provided on when to use this tool versus alternatives (e.g., when to remove vs. modify a transition), nor are prerequisites mentioned. The 'Compatibility tool' label hints at special usage constraints but fails to explain them, leaving the agent without actionable guidance.

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