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 offers only the cryptic 'Compatibility tool' hint without explaining what that implies for behavior, state changes, or return values. It does not clarify what the 'autoConnect' parameter connects to, or what happens during the timeout period.

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 appropriately brief at two fragments, the second fragment '(Compatibility tool)' wastes space by providing a label without context or explanation. The description is front-loaded with the action, but the parenthetical creates confusion rather than value.

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 that this tool has parameters with zero schema documentation, no annotations, and no output schema, the description is insufficiently complete. It fails to describe the return structure (critical for a 'get' tool), the connection behavior implied by 'autoConnect', or the legacy/compatibility nature of the tool.

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' and 'autoConnect'), yet the description provides no compensatory information about what these parameters control, their units, or their behavioral implications. The agent must guess the purpose of a timeout and auto-connection logic in this context.

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 ('Get') and resource ('audio bus layout'), but the parenthetical '(Compatibility tool)' introduces ambiguity without explanation—it's unclear if this indicates deprecation, legacy support, or backward compatibility requirements. It also fails to differentiate from the sibling tool 'get_audio_info'.

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 like 'get_audio_info' or 'add_audio_bus'. There is no mention of prerequisites, side effects, or exclusion criteria that would help an agent determine if this is the correct tool for their current task.

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