current_playhead

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

No annotations are provided, so the description carries full burden. It does not disclose return format, potential null/error cases, or whether the tool depends on a valid timeline. The simple statement lacks behavioral context beyond the basic action.

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, concise sentence of 6 words with no filler. Every word is necessary, and the important information is front-loaded ('Return the active timeline playhead timecode').

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 has no parameters and an output schema (not shown), so the description doesn't need to explain return values. The description is sufficient for a simple getter, though it could mention the timecode format for added clarity. It covers the essential purpose.

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?

With zero parameters and 100% schema coverage (trivially, since there are none), the baseline is 4 per the rubric. The description adds no parameter info as there are none to describe.

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 tool returns the active timeline playhead timecode. The verb 'return' and resource 'active timeline playhead timecode' precisely define the function. This distinguishes it from siblings like 'jump_to_timecode' (which moves the playhead) and 'current_clip' (which returns clip info).

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 tool versus alternatives like 'jump_to_timecode' or 'current_timeline'. The description does not specify prerequisites (e.g., must have an active timeline) or conditions under which the tool should or should not be used.

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