seek

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 behavioral disclosure. It conveys the core action but does not mention behavior for out-of-range positions, whether playback continues after seeking, or if the seek fails when no track is playing. This is a meaningful gap for a state-changing playback control.

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, tight sentence with no filler. The core verb, target resource, and parameter semantics are all front-loaded, making it easy for an agent to parse quickly.

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: one required parameter, no nested objects, and an output schema is present. The description provides enough for basic invocation, though it omits edge-case behavior and explicit usage guidance. These omissions are minor given the low complexity.

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 clarify the parameter. It does add crucial meaning by identifying position_ms as 'a position (in milliseconds)', which maps the parameter to the seek target. It does not provide valid ranges, bounds, or negative-value semantics, but for a simple millisecond integer this is adequate.

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 names a specific verb ('seek'), a specific resource ('currently playing track'), and the unit of measurement ('milliseconds'). This clearly distinguishes it from sibling controls like skip_next and skip_previous, which move by track rather than by time position.

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 phrase 'currently playing track' implies the tool requires active playback and is intended for jumping to a precise time position. However, it does not explicitly state when to choose this over skip_next/skip_previous or mention any prerequisites like having an active playback session.

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