ledfx_set_audio_device

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

No annotations are provided, and the description does not disclose behavioral traits such as whether setting the audio device affects other audio processes, if it requires authentication, or potential side effects like restarting the audio engine.

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 unnecessary words, effectively conveying the core action.

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 simple setter with one parameter and no output schema, the description is adequate but lacks context on prerequisites (e.g., needing devices detected) and side effects. It does not fully compensate for the lack of annotations.

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?

While the parameter 'device_index' has a description in the schema ('Audio device index'), the tool description adds no extra meaning. It does not explain how to obtain or validate the index, missing an opportunity to clarify the parameter semantics.

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 'Set the active audio input device' uses a specific verb ('Set') and resource ('active audio input device'), clearly distinguishing it from sibling tools like 'ledfx_list_audio_devices' and 'ledfx_find_devices'.

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 or alternatives. For instance, it doesn't mention that users should first list available audio devices to obtain the correct index, or that this tool might interrupt audio playback.

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