set_song_time

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

With no annotations, the description must fully disclose behavioral traits, but it only repeats the core action. It does not mention side effects on playback, valid time ranges, whether the command works when the transport is stopped, or any error conditions. This is insufficient behavioral information.

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 concise: one purpose sentence plus a compact parameter explanation. It is front-loaded with the action and contains no redundant or unrelated content.

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?

The tool is simple, and the description covers the action and parameter. However, with no annotations and no mention of behavioral context (e.g., what happens if the song is not playing, whether the position is absolute or relative), there are noticeable gaps. The output schema is provided, so return values need not be described, but the behavioral context is incomplete.

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 schema provides only a type and title for 'time', but the description's Args section adds the semantic meaning: 'Position in beats to jump to.' This fully compensates for the 0% schema description coverage and gives the agent a clear understanding of the parameter.

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 action: 'Set the current song time (playhead position) in beats.' This provides a specific verb and resource, making the purpose unambiguous. It does not explicitly differentiate from sibling tools like get_song_time, but the verb 'set' against 'get' conveys the write action.

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?

There is no guidance on when to use this tool versus alternatives such as get_song_time or set_tempo. The description lacks any contextual use cases, prerequisites, or exclusions, so the agent receives no direction on appropriate invocation.

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