set_default_sink

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows it mutates state non-destructively; the description adds nothing beyond that. It doesn't say whether the change persists across sessions, what happens with an unknown sink name, or whether the current default is returned.

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?

One short sentence with the action and identifier forms front-loaded and zero filler.

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 one-parameter setter with annotations and no output schema the essentials are present, but the description omits how the agent obtains a valid sink identifier and what the call returns or changes on failure — practical gaps for an agent using this cold.

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?

Schema description coverage is 100% and the single parameter 'sink' is documented as 'Sink name or numeric ID', matching the description. Baseline 3 applies since the schema already carries the parameter meaning.

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?

Specific verb ('Set') plus resource ('default audio output device') with the accepted identifier forms (name or ID). The one thing it doesn't do is distinguish itself from the sibling set_default_source, which differs only in source-vs-sink — the description never says 'output, not input'.

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?

Usage is implied by 'audio output device', but there's no explicit guidance such as 'call list_audio_sinks first to discover valid names' or when to prefer this over set_default_source. An agent must infer the workflow.

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