get_playback_position

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

With no annotations provided, the description must disclose behavioral traits on its own. It only states what is retrieved but does not confirm it is side-effect-free, specify the units of the position (e.g., beats, seconds), or enumerate possible transport states. This adds little beyond the tool name, making the description insufficiently transparent for a tool with zero annotation support.

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, direct sentence that leads with the verb and clearly identifies the returned information. It contains no filler, repetition of the tool name, or unnecessary words—every part contributes to understanding the tool's function.

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 getter with no parameters and no output schema, the description gives the general semantic content but lacks specifics such as the format of the playback position or the exact values of the transport state. This leaves some ambiguity about the response, making it minimally viable but not fully complete.

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 are no parameter semantics to clarify. According to the baseline rule for 0-parameter tools, a score of 4 is appropriate since the description is not required to explain parameter details and the schema already reflects no inputs.

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's function with a specific verb ('get') and resource ('current playback position and transport state'). This cleanly distinguishes it from sibling tools like start_playback and stop_playback, leaving no ambiguity about its purpose.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that this is the read-only counterpart to playback control tools, nor does it exclude cases like when the transport is stopped or how it relates to jump_to_time. The agent is left without explicit decision criteria.

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