seek_media

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

Annotations already convey that the operation is not read-only and not destructive. The description adds that it changes the playback position, but it does not disclose potential side effects or prerequisites, such as requiring active media playback or behavior when no media is available.

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 sentence with no filler; the core action, resource, and unit are all front-loaded. Every word contributes to the agent's understanding.

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 one-parameter action tool, the description is largely complete: it names the operation and the parameter's role. The only notable gap is the lack of any statement about return behavior or failure conditions, which is minor given the tool's simplicity and existing annotations.

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?

With 0% schema description coverage, the description compensates by clarifying the sole parameter: the target position in seconds. It establishes that 'seconds' is an absolute position rather than a relative offset, adding meaning beyond the bare property name and type.

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') and resource ('media playback') and specifies the unit ('in seconds'), making the tool's function clear. It does not explicitly name siblings, but the absolute-position semantics distinguish it from related controls like next_track or toggle_play_pause.

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 the use case—jumping to a specific playback position measured in seconds—but does not explicitly state when to prefer it over alternatives or mention exclusions. For example, it does not clarify that it should be used for absolute seeks rather than relative skips.

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