itunes_set_device

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action ('switch audio output') but does not mention potential side effects, error cases (e.g., device not found), reversibility, or any required state. For a simple switching tool, this is minimally adequate but leaves behavioral nuances unaddressed.

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 two sentences, front-loaded with the action and parameter meaning. Zero fluff, every word contributes value. It's exemplary in conciseness.

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 a single parameter, no output schema, and no annotations, the description covers the essential action and parameter. It could optionally mention that device names come from list_devices or that the tool requires the device to be available, but it's largely complete for its simplicity. Slight gap in failure-mode context.

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 coverage is 0% (parameter only has a title 'Device Name' with no description). The tool description adds 'The exact name of the AirPlay device' and provides examples, which clarifies that the name must be exact and how to identify valid values. This compensates for the lack of schema description.

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 ('Switch audio output to a specific AirPlay device by name') with specific examples (HomePod, AirPods, TV). This distinguishes it from sibling tools like set_volume (adjust volume) and list_devices (list devices), making the purpose unambiguous.

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?

The description implies usage: when you want to set the audio output device by name. It doesn't explicitly mention alternatives or when not to use, but within the context of sibling tools (e.g., list_devices to find names), it provides enough clarity. No explicit exclusions or prerequisites are given.

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