Add audio effects to Godot buses to control sound processing and mixing in game projects.
Add effect to audio bus. (Compatibility tool)
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "add_audio_bus_effect"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| timeoutMs | No | ||
| autoConnect | No |
Changes observed during successful MCP inspections.
v0.1.0Does 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 provides minimal context. The 'Compatibility tool' label hints at behavioral constraints (possibly deprecation or legacy support) but remains unexplained. No information about side effects, prerequisites (e.g., bus must exist), or failure modes.
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 (6 words), this is underspecification rather than efficient conciseness. The parenthetical '(Compatibility tool)' consumes space without earning its place—providing a cryptic classification without explanation. The description lacks the necessary detail for an agent to invoke the tool correctly.
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 the specialized domain (audio effects in Godot), 0% schema coverage, and 'additionalProperties' allowing arbitrary parameters, the description is grossly incomplete. It fails to document required parameters, expected effect types, or return behavior, leaving the agent without sufficient context to construct valid invocations.
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?
Critical failure: schema has 0% description coverage and allows 'additionalProperties: true', indicating significant parameters (likely 'bus_name', 'effect_type') are not defined in the schema. The description completely omits all parameters including the two defined ones ('timeoutMs' and 'autoConnect'), failing to explain what operation times out or what gets auto-connected.
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 effect to audio bus') but remains vague about what constitutes an 'effect' in this context (e.g., reverb, delay, EQ). It fails to differentiate from the sibling tool 'add_audio_bus', which creates the bus itself versus adding effects to an existing bus.
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 'set_audio_bus' or 'get_audio_bus_layout'. The parenthetical '(Compatibility tool)' suggests special usage constraints but offers no explanation of what they are or when this should be preferred over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.