transport_get_play_position

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

No annotations provided, so description carries full burden. Adds crucial behavioral detail 'in seconds' (unit of measurement) not present in schema. However, omits read-only confirmation, return data type (float vs integer), and behavior when playback is stopped vs active.

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?

Single sentence with zero waste. Front-loaded with action verb and precisely scoped with unit specification. 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?

Appropriate for low-complexity tool with zero parameters. Specifies the return value unit (seconds), compensating somewhat for missing output schema. Could improve by indicating return type (number) or that it reflects the playhead/transport position.

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?

Zero parameters present, establishing baseline 4. Description correctly requires no parameter explanation, though it effectively implies the tool requires no inputs to retrieve the current state.

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?

Specific verb 'Get' and resource 'playback position' clearly identify the function. The 'in seconds' qualification distinguishes the return format and scope from cursor-related siblings like transport_set_cursor.

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?

Implies usage through the verb 'Get' (use when needing to query position), but lacks explicit when-to-use guidance or differentiation from similar tools like cursor_set_position or transport_set_cursor.

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