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 behavioral disclosure burden. While 'Configure' implies mutation, the description fails to explain what '(Compatibility tool)' means regarding side effects, deprecation status, or state changes. No information on idempotency or safety is provided.

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 extremely brief (9 words) and front-loaded with the verb. However, given the complete lack of structured documentation elsewhere, this brevity becomes under-specification rather than efficient communication.

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 zero schema descriptions, no annotations, and no output schema, the tool requires a descriptive burden that the text fails to meet. The cryptic 'Compatibility tool' note raises questions without answering them, and the parameter semantics are left entirely unexplained.

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, the description must explain the two parameters ('timeoutMs' and 'autoConnect'), but it does not. It vaguely references 'properties' without mapping them to the actual parameters or explaining the 'additionalProperties: true' pattern for arbitrary bus property configuration.

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 core action ('Configure') and target ('audio bus properties'), but fails to distinguish from sibling 'add_audio_bus' (creation vs. modification). The '(Compatibility tool)' annotation is present but unexplained, leaving the scope and intent ambiguous.

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 provided on when to use this tool versus 'add_audio_bus', 'get_audio_bus_layout', or 'get_audio_info'. The 'Compatibility tool' parenthetical hints at special usage but provides no actionable criteria for selection.

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