set_song_time

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

The description lacks detail on behavioral traits. For example, it does not disclose whether the song must be playing, if playback state changes, or if the seek is absolute. Without annotations, this is a significant 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?

Two sentences with no wasted words. The parameter description is integrated efficiently.

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 simple seek tool with one parameter and an output schema, the description is minimally adequate. It covers the basic action and parameter but omits behavior details like impact on playback or looping.

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?

The description adds value by explaining 'Position in beats from the start', providing context beyond the schema's bare 'number' type. Schema coverage is 0%, so the description compensates well. However, it does not specify constraints like non-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's purpose with a specific verb ('Jump') and resource ('position in the song'). It distinguishes from siblings like playback controls and tempo settings.

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 is provided on when to use this tool versus alternatives such as jump_to_cue_point or start_playback. The agent receives no context for selection.

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