itunes_repeat

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

With no annotations, the description carries the disclosure burden. It explains the effect of each mode ('off', 'one', 'all') but does not mention persistence, side effects on current playback, or behavior when an invalid mode is passed. It adequately describes the core mutation but lacks deeper behavioral context.

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 extremely concise, with one action sentence followed by a clear argument listing. Every word earns its place, and there is no redundant or vague 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?

Given the tool's low complexity—one simple parameter, no output schema, and clear sibling context—the description is mostly complete. It defines the action and all mode semantics, though adding the default value or noting optionality would make it fully self-contained.

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 0%, so the description must fully explain the parameter. It does this by enumerating all valid mode values with parenthetical explanations. However, it omits the default value ('all') already present in the schema and does not explicitly state that mode is optional, slightly reducing completeness.

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 tool's function with a specific verb and resource: 'Set playback repeat mode.' It distinguishes this from sibling tools like itunes_set_shuffle_mode by focusing specifically on repeat behavior, and the three mode values clarify scope.

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 provided about when to use this tool versus alternatives. It does not mention that itunes_set_shuffle_mode handles shuffle, nor does it state exclusions or prerequisites. The context is implied but not explicit.

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