Seek

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains that seeking is relative to the track start, but does not disclose what happens if seconds exceeds the track length, how seeking interacts with play/pause state, or whether any state change is reported back.

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?

A single, front-loaded sentence contains the essential behavior without redundancy. It is appropriately concise and every word earns its place.

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?

This is a simple tool, so the description is almost adequate, but it does not mention return values, error handling, or what occurs when the seek position is invalid or when no track is active. Agents will have to infer these behaviors from context.

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 description adds meaningful semantics for the required seconds parameter by defining it as 'seconds from start' in the current track. The optional player parameter is already documented in the schema, so both parameters end up with adequate meaning.

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 uses a specific verb (Seek), identifies the resource (current track), and clarifies the unit of the position (seconds from start). This makes it easy to distinguish from sibling tools like play_music or now_playing, and even from the broader playback_control.

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 the tool: when the agent needs to move to a specific position in the current track. However, it gives no explicit guidance about when not to use it, nor does it point to alternatives like playback_control for related playback actions.

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