transport_song_length

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

With no annotations, the description must carry behavioral disclosure; 'Return' does signal a read-only query and lists the output units. However, it does not state how the five units are packaged in the response or whether the value reflects the active project/current arrangement, leaving some behavior implicit.

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 front-loaded sentence with no filler: it states the action, object, and units in eleven words. Every word earns its place.

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 parameterless getter this is nearly complete: the purpose, read-only nature, and units are all present. It would be slightly stronger with a note on the return shape, since no output schema exists, but the low complexity makes the description adequate for selecting and invoking the tool.

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?

There are zero parameters, so the empty schema is fully self-descriptive and the baseline is 4. The description adds useful context by naming the units the returned length is expressed in, though it has no parameter meanings to clarify.

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 ('Return') and names a concrete resource ('song length') with five explicit units. This clearly distinguishes it from sibling commands such as transport_set_position or transport_status, which set or report different transport state.

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 intended use is immediately clear: call this zero-argument tool when the song length is needed. It does not name alternatives or counter-indications, but no sibling tool provides the same query, so the absence of explicit routing is not a material gap.

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