godot_set_bus_effect

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

Annotations indicate a non-readonly, non-idempotent, non-destructive mutation, which the description aligns with via 'Add or adjust'. However, the description adds little beyond what annotations already imply. It does not mention side effects like whether changes persist or if the layout file is modified unless explicitly requested via parameters. No contradiction with annotations.

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 a single, concise sentence with no filler. The main verb and object are front-loaded, and it is immediately clear what the tool does. Nothing extraneous is included.

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?

For a tool dealing with audio effects on buses, the description omits key context such as whether the bus must already exist, what happens if the effect is already present, or how 'adjust' behaves with existing effects. The annotations are all false/default, providing no safety net. The lack of any usage context or return behavior leaves a significant gap for an agent to invoke this correctly.

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 schema has 0% description coverage for its parameters; the tool description does not mention any parameter names, types, or relationships. The schema itself is well-documented, but the description provides no compensation. This forces an agent to rely entirely on the schema, which is a significant gap.

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 clearly states the action ('Add or adjust') and the resource ('real-time audio effects on an audio bus'). It is distinguishable from related tools like godot_configure_audio_bus and godot_get_audio_layout. The wording is specific and immediately understandable.

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. There is no mention of scenarios requiring effect management as opposed to bus configuration, nor any conditions under which this tool should be preferred. The description gives no context on prerequisites or typical use cases.

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