transport_get_play_position

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'Get' implies a non-mutating read, and the description explicitly lists what state is returned. It does not mention units or response format, but for a zero-parameter state getter this is a reasonable level of transparency.

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, front-loaded sentence that names the operation and all returned state with no filler. Every word contributes meaning, and a reader can absorb the entire purpose in seconds.

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 zero-parameter getter with no output schema, the description covers the essential invocation context: what the tool retrieves and that it is a state inspection. The only minor gap is the lack of units or formatting details for positions, but this is not critical enough to make the tool unusable.

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 tool has zero parameters, so there is nothing for the description to clarify beyond what the empty schema already shows. Per the rubric, zero params receive the baseline score of 4; no further parameter documentation is needed.

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 specific action ('Get') with a clear resource ('current playhead position') and enumerates the exact state being retrieved: playback active status and time selection start/end. This differentiates it from sibling transport controls like transport_play, transport_stop, and transport_record, which are commands rather than queries.

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 getter phrasing conveys clear context: this tool is for inspecting transport state, not for changing it. It does not explicitly name alternatives or exclusion cases, but among the many transport_* siblings its read-only purpose is immediately recognizable, so an agent can decide when to invoke it without much ambiguity.

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