Godot MCP Bridge

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

No annotations are provided, so the description carries full burden. It discloses nothing about side effects (what happens if the bus exists), return values, authentication needs, or what 'compatibility' implies for behavior. For a state-mutating operation, this is a critical gap.

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, the description is under-specified rather than elegantly concise. The second sentence '(Compatibility tool)' consumes space without earning it—lacking context, it confuses more than clarifies. The parameters and behavioral details are entirely omitted.

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 2-parameter state-mutating tool with zero schema documentation, no annotations, and no output schema, the description is inadequate. It fails to explain Godot-specific audio bus concepts, parameter interactions, or success/failure behaviors required for safe 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?

Schema description coverage is 0% (timeoutMs and autoConnect are undocumented), yet the description provides no compensatory information. It does not explain what the timeout applies to, what auto-connects to what, or provide usage examples for these two parameters.

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') and resource ('audio bus'), but the parenthetical '(Compatibility tool)' is vague and unexplained. It fails to distinguish from siblings like 'add_audio_bus_effect' or 'set_audio_bus', leaving ambiguity about which audio bus tool to use.

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 on when to use this tool versus alternatives like 'set_audio_bus' or 'get_audio_bus_layout'. The 'Compatibility tool' note hints at special usage constraints but provides no actionable information about when/when-not to use it.

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