set_cursor_position

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

Annotations provide destructiveHint=false, which covers the safety profile. The description adds no further behavioral context (e.g., that it moves the cursor without affecting playback or selection). For a trivial setter, this is acceptable but does not enrich beyond the annotation.

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 two short sentences: a terse statement of the action followed by a clear parameter definition. No filler, and the most critical information is front-loaded.

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 setter with no output schema and a low-complexity operation, the description provides everything needed to call it correctly. It could optionally mention side effects, but none are essential.

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 only defines 'position' as a number with no description. The description compensates fully by specifying 'Position in seconds from project start,' giving both the unit and the origin, which is essential for correct invocation.

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 states a clear verb ('Set') and a specific resource ('the edit cursor position'). It implicitly differentiates from the sibling get_cursor_position by contrasting set vs. get, so an agent can immediately identify the 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?

The purpose is self-evident for a setter, but no explicit when-to-use guidance or mention of the get_cursor_position alternative is provided. Usage is implied rather than stated, which is adequate for a simple tool but leaves no explicit exclusions.

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