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

Annotations declare readOnlyHint=false, which is unusual for a GET-shaped tool, and the description explains exactly why by disclosing that it assigns and saves stable IDs as a side effect. That is genuinely additive behavioral context beyond the annotation. It doesn't say whether that write is idempotent or whether it requires elevated permissions, so it is not a full 5.

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?

Three tight sentences: purpose first, the non-obvious side effect second, and the mirrored REST endpoint last. Every sentence carries information, though the REST endpoint reference is of marginal value to an agent.

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 two-parameter read tool with no output schema, the description covers what is returned ('ordered items') and the one surprising behavior (ID assignment). It leaves the returned item shape and ordering stability unstated, but the annotations plus schema fill most of the remaining gaps.

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 description coverage is 100% and the enum values for 'type' are fully documented in the schema, so the description adds no parameter-level meaning. The description mentions 'legacy external-video items' but doesn't tie that to the external-videos enum value. Baseline 3 applies.

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?

States a specific verb and resource ('Get the ordered items of one of a stream's media queues') and scopes it to one queue type, which is precise enough to distinguish it from add_to_stream_queue and remove_from_stream_queue. It stops short of explicitly naming the siblings an agent should compare against, so it lands just under the top band.

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?

Usage is only implied: the description notes the returned IDs let items be 'targeted by playback and removal tools,' which hints that this is the discovery step before play/skip/remove. There is no explicit when-to-use statement or rule for choosing among the sibling queue tools.

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