transport_set_position

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

No annotations are provided, and the description only says 'Set cursor position.' It does not disclose whether playback continues, pauses, or if the cursor movement is instant. This is insufficient for an agent to understand side effects.

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 extremely concise with only two lines, front-loading the action. Every sentence is necessary and no filler is present.

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?

Given the lack of output schema, low parameter description coverage, and no annotations, the tool description is too minimal. It omits important details such as whether the tool works during playback or recording, and what the expected behavior is when setting an out-of-range position.

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 adds 'Position in seconds' to the seconds parameter, providing meaning beyond the schema's type and title. However, it does not clarify allowed range or format (e.g., floating-point, negative values).

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 the tool sets the cursor position, using the verb 'Set' and the resource 'cursor position'. It distinguishes from sibling tools like transport_play and transport_stop, which control playback state, not 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?

No guidance on when to use this tool versus alternatives such as transport_play or transport_get_state. The description lacks context like 'use this to jump to a specific time' or comparison with other transport tools.

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