Seek media

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

Annotations provide only false hints, so the description carries the behavioral disclosure burden. It does not mention side effects on playback, whether the media input must exist or be playing, clamping behavior, or whether repeated seeks accumulate. It only restates the core seek operation without adding 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 a single sentence with no wasted words. It front-loads the core action and immediately communicates the key mode distinction, making it easy to parse and act on.

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?

With an output schema present and mediaId/mediaName already documented, the description is adequate for basic invocation. Yet it lacks sibling differentiators, usage context, and behavioral side effects, which are important given the large set of closely related media tools. It is minimally viable but not fully complete.

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 50%, and the description adds useful meaning for `milliseconds` (millisecond cursor) and `mode` (absolute vs relative). However, it does not clarify whether mediaId and mediaName are alternatives, which takes precedence, or how they relate to the required `milliseconds`, so it only partially compensates for the schema's gaps.

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 a specific action ('Seek a Media Source') and precisely defines the two behaviors: seeking to an absolute millisecond cursor or applying a relative offset. It is unambiguous about the resource being seeked, but it does not explicitly differentiate this from closely related siblings like media_play_range or media_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?

There is no guidance on when to use media_seek versus alternative sibling tools such as media_play, media_play_range, or media_control. The description explains what the tool does, including the absolute/relative modes, but does not state prerequisites, exclusions, or alternative selection criteria.

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