seek

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

With no annotations, the description carries the full behavioral burden. It does not say whether a track must be actively playing, whether seeking works while paused, what happens with no active device/track, or whether the position is clamped to track length. For a playback-mutating control, that is a notable gap.

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 sentence, front-loaded with the action and including the unit inline. Nothing is wasted, though it is minimal enough that it reads as under-specified rather than deliberately tight.

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 single-parameter tool with no output schema, the description covers the core action and unit, but omits the operational preconditions (active playback, error behavior) that an agent would need to invoke it reliably.

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% and the sole parameter 'ms' is undocumented in the schema, so the description must compensate. It does the essential job by naming the unit (milliseconds) and the reference point (position in the current track), which is the key semantic an agent needs.

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?

Specific verb ('Seek to a position') plus resource ('the current track'), and it implicitly distinguishes itself from sibling transport controls like skip, previous, and play by acting on a position within the current track rather than changing tracks. It stops short of naming those siblings explicitly.

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 statement of when to use this versus skip/previous/play, nor any prerequisite such as an active playback session. Usage is only inferable from the word 'current track'.

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