Move Playhead To Edit

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, and the description adds nothing beyond them — no mention that this mutates the playhead position without editing content, nor any indication of what happens if no edit point exists in the requested direction.

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?

A single tight sentence with the action front-loaded and zero filler. It's appropriately sized for a one-parameter navigation tool, though it could carry a bit more routing information at the same length.

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-param navigation tool with an output schema and full schema coverage, the description is minimally adequate. It doesn't address behavior at sequence boundaries or clarify positioning relative to siblings, which would be useful given how many playhead/edit-point tools exist.

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 description coverage is 100% and the single 'direction' parameter is a documented enum with a stated default, so the schema fully carries parameter meaning. The description echoes 'next or previous' but adds no semantics beyond the schema.

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?

States a specific verb ('move') and resource ('the playhead') with scope ('to the next or previous edit point'). This is clear enough to distinguish it from siblings like set_playhead_position or navigate_playhead, though it doesn't explicitly name those alternatives.

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 on when to use this versus adjacent sibling tools such as get_next_edit_point, navigate_playhead, or set_playhead_position. The agent must infer the appropriate context from the name alone.

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