loop_current_track

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

With no annotations, the description carries the full disclosure burden, and it does convey the key trait that looping persists 'indefinitely' — a state change on the player. It omits whether the call is idempotent, what happens if a track is already looping, and how to undo it (the stop_looping sibling).

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 that front-loads the action and contains no filler or redundancy.

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-arg toggle with an output schema present, the description is minimally sufficient, but the lack of any pointer to stop_looping or to player-state preconditions leaves an agent to infer the off-ramp.

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 takes zero parameters, so there is nothing to document and no schema gap to compensate for; the description correctly avoids inventing inputs.

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?

A specific verb ('Locks ... to loop') plus a precise resource ('the current track') makes the effect unambiguous. It does not, however, distinguish itself from the sibling stop_looping, which is the obvious inverse operation an agent would need to consider.

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?

There is no explicit guidance on when to call this versus stop_looping or a queue-based repeat mode; usage is only inferred from the name. No prerequisites (e.g., a track must be playing) are stated.

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