skip_music_track

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states the basic action and does not mention side effects, behavior at the start/end of a queue, whether playback is affected, or other consequences. This lack of detail leaves the agent uncertain about the tool's full impact.

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, front-loaded sentence with no wasted words. It efficiently conveys the essential action and parameter direction.

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?

The tool is simple with one parameter and no output schema. However, the description lacks important context such as queue boundary behavior or whether the tool starts playback, which are relevant for a music control action. While not overly complex, the missing behavioral details reduce completeness.

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 input schema fully describes the 'direction' parameter with an enum and a short description. The description adds minimal value beyond mapping 'next'/'previous' to the intended behavior, but since schema coverage is 100%, the parameter meaning is already clear.

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 ('Skips') and the resource ('track in Apple Music'), and specifies the direction parameter ('next or previous'). This distinguishes it from sibling music tools like play_pause_music or set_music_volume, which handle different actions.

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 when to use this tool (when you want to change tracks), but it does not explicitly contrast with alternatives or mention edge cases. Since sibling tools are different actions, the usage context is clear but not elaborated.

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