set_song_time

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

With no annotations, the description must carry the transparency burden. It does not mention side effects (e.g., whether playback pauses or continues), error conditions, or the effect on the current playing state. However, the parameter descriptions clarify the expected values, which partially compensates.

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 succinct, with no unnecessary words. It includes the single action and parameter explanations in a compact format, making it easy to parse.

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 description adequately covers the tool's purpose and parameters. It does not mention return values, but for a simple seek operation, that is not critical. The absence of side-effect information is a minor gap, but the overall description is sufficient for an agent to use it correctly.

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 semantic detail beyond the schema by specifying that bar is 1-based and beat is 0-based, and explains their precedence. This fully clarifies the meaning of both parameters, achieving 100% coverage.

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 action ('Jump') and the target ('playback to a position'), which is distinct from other set_* tools like set_tempo or set_clip_property. It precisely identifies the tool's primary function.

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 implicitly indicates when to use it: when you need to move the playback position. It doesn't explicitly list alternatives or exclusions, but the context of 'jump playback' is sufficient for most use cases.

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