itunes_play

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

With no annotations and no output schema, the description must carry the behavioral explanation. It states the primary effect—starting playback—but it does not disclose behavior when playback is already active, whether it resumes the current track, or what the return state is. This is acceptable but minimal.

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 sentence, uses an active verb, and includes just enough context about the target application. There is no verbosity or repetition.

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 zero-parameter play command, the description is largely sufficient. It supplies the basic operation and the target app. It could be more complete by noting that it starts the current playback context or requires a track to be present, but the current content is enough in most cases.

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 tool has zero parameters and the input schema is empty, so the description does not need to clarify parameter formats. The baseline score of 4 for no parameters applies because there is nothing else for the description to add.

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 uses a specific verb and resource: 'Start playback in Music (iTunes)' clearly names the action. It is not explicit about how it differs from the sibling itunes_play_song, but the zero-parameter schema plus general 'start playback' wording make the core purpose 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 given about when to use itunes_play versus itunes_play_song, itunes_pause, or itunes_next. The description does not mention context such as resuming paused playback or starting the default queue.

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