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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description need not restate safety. It adds real value by clarifying replace semantics (the supplied list becomes the queue order, and it must be complete) and by mapping to the underlying PATCH endpoint, though it does not say what happens to items omitted from the list.

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?

Two tight sentences with zero filler; the core replacement semantics are front-loaded and the API mapping is secondary. Nothing extraneous.

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 3-parameter, no-output-schema mutation tool with full schema coverage and safety annotations, the description covers purpose and semantics adequately. A brief note on what happens to queue items omitted from the new order would make it 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?

Schema description coverage is 100%, with each parameter (stream, type enum, order) documented in the schema itself. The description only reinforces that 'order' must be the complete ordered list of ids, adding marginal meaning over the schema, so the 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 (Replace) and resource (a stream queue's playback order) with the input shape ('full ordered list of item ids'), which clearly separates it from add_to_stream_queue and remove_from_stream_queue. It does not name those siblings explicitly, so it falls just short of a 5.

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 phrase 'full ordered list' implies this is the tool for wholesale reordering rather than incremental add/remove, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative. Usage is only implied.

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