transport_set_cursor

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

With no annotations and no behavioral details beyond the basic action, the description fails to disclose important traits such as whether playback is affected, what happens with invalid time values, or any side effects. This forces the agent to guess.

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 sentences, front-loading the action and parameter. Every word serves a purpose, and there is no extraneous 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?

For a simple one-parameter tool, the description is nearly complete but lacks differentiation from a similar sibling and does not cover error conditions or effect on playback. It meets the minimum viable standard.

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 0%, so the description must fully explain parameters. It states 'time: Position in seconds', which adds the unit but no range, format, or constraints. This is minimally helpful but insufficient for a single 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 verb ('Set') and resource ('playback cursor position'), making the action unambiguous. However, the presence of a sibling tool 'cursor_set_position' with a similar name creates potential confusion, and the description does not differentiate them.

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 like 'cursor_set_position' or other transport tools. The description lacks any context about appropriate usage scenarios or prerequisites.

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