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

Annotations declare a destructive, non-read-only, open-world mutation, and the description adds real context beyond them: it 'requests a change to live output', repeating the command can restart the item, and the 202 'acknowledges an asynchronous request, not confirmed playback'. That async/non-confirmation nuance is exactly the kind of behavioral disclosure an agent needs and cannot get from annotations.

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?

Purpose is front-loaded, followed by behavioral caveats, the prerequisite for item_id, and the underlying API semantics. Every sentence carries distinct information with no filler.

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 mutation tool with no output schema, the description is complete: it covers purpose, preconditions, live-output side effects, repeat behavior, and explicitly explains that the 202 is an async acknowledgment rather than confirmed playback. An agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds provenance for item_id ('Get item_id from get_stream_queue'), telling the agent where the identifier comes from rather than just that it exists. This is a meaningful addition over the schema text.

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 verb+resource: 'Jump to a playable item already in an active stream queue, starting it from the beginning without restarting the stream.' It clarifies the scope (must already be in an active queue) and the key behavioral distinction (playing from start vs restarting), which separates it from skip/reorder siblings.

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?

It implies the precondition (item must already be in an active stream queue) and points to get_stream_queue for obtaining item_id, giving usable context. However, it never explicitly contrasts with siblings like skip_stream_queue or reorder_stream_queue, so the 'when to use this vs alternatives' decision is left to inference.

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