transport_seek

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety and repeatability are covered elsewhere. The description adds only the beat-origin convention (0 = song start) and says nothing about the effect on ongoing playback or whether other transport state is altered, which is the main behavioral question for a seek.

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?

One short sentence with the action first and the origin convention second; no filler and nothing that could be trimmed without losing information.

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 seek with full schema coverage and annotations carrying the safety profile, this is close to sufficient. The only meaningful gap is that it does not say what happens to playback if the transport is running when the playhead moves.

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 coverage is 100% and the single parameter is already documented as 'Song position in beats.', so the baseline would be 3. The description earns an extra point for clarifying that 0 maps to song start and that positions are absolute in beats rather than relative offsets, which the schema does not state.

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?

States a specific verb ('Move') and resource ('the playhead') plus the unit of the target position (beats), which is exactly what an agent needs to distinguish it from transport_play/stop/get. It does not explicitly name a sibling, but the resource+action pairing is unambiguous in a transport_* family.

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?

Usage is implied by the naming and the '0 = song start' hint, so an agent can infer this positions the playhead rather than starting or stopping playback. However there is no explicit statement of when to prefer this over transport_play or transport_get, and no note on whether it must be called while stopped versus playing.

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