transport_set_position

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 states the action but does not say whether seeking stops or continues playback, whether the change is immediate, or what side effects might occur. For a mutating transport operation, this is a notable transparency 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?

The description is a single front-loaded sentence with no filler or redundant information. Every word contributes to conveying the tool's purpose.

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 transport-mutating tool with no annotations, no output schema, and no parameter descriptions, the description is too thin. The schema covers the required parameter and the unit enum, but the agent is left without guidance on units' effect on the position value or the operation's impact on playback state.

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%, and the description does not explain how 'position' relates to the 'unit' field or what value ranges are expected. It adds only minimal meaning beyond the schema by clarifying that the position refers to a location in the song.

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 ('specific position in the song'), which clearly distinguishes this from sibling transport tools like transport_play, transport_stop, and transport_jog. Even without the schema, an agent can understand exactly what operation this performs.

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 tool is used when the playhead needs to move to an exact position, but it provides no explicit guidance on when to choose this over alternatives such as transport_jog or transport_set_loop_mode. Usage context is present only by implication, with no exclusions or alternative routing.

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