get_playhead_position

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

The description does not disclose return format (e.g., seconds, timecode), units, error behavior on invalid sequenceId, or whether the sequence must be active. With no annotations provided, the description carries the full burden but offers only the basic fact that it retrieves a position.

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 a single sentence that is front-loaded with the action and resource. It contains no filler or redundant information, making it highly concise and efficient.

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 with one param and no output schema, but the description does not mention what the returned position represents or its format. Given the absence of annotations and output schema, additional detail about the return value would be necessary for full contextual completeness.

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 already documents sequenceId as 'The ID of the sequence' with 100% coverage. The description adds no further meaning beyond paraphrasing 'specified sequence' to the parameter, so it stays at the baseline of 3 for high schema 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 uses a specific verb (Gets) and resource (current playhead position) tied to a specified sequence. This clearly distinguishes it from sibling tools like set_playhead_position (setter) and get_source_monitor_position (source monitor, not sequence).

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 descriptor 'in the specified sequence' implies this tool is for sequence playhead positions, but it does not explicitly compare to alternatives such as get_source_monitor_position or state when to prefer this over similar getters. No exclusions or alternative recommendations are provided.

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