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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond them: it scopes the destruction ('The media file itself is not deleted') and warns of a live side effect ('Queue changes can affect live output') that the annotations do not express.

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, zero filler, with the identification semantics front-loaded before the caveats and the endpoint reference last. Every sentence carries distinct information.

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 mutation tool with full schema coverage, existing annotations and no output schema, nothing an agent needs is missing: the identifier ambiguity, the non-destructive-to-file guarantee, and the live-output risk are all stated.

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 and the schema already documents all three parameters. The description goes further by explaining that mediaId is a media UUID for storage queues but a queue item id for external-videos, adding meaning the schema description does not supply.

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+resource ('Remove one item from a stream queue by its id') and immediately disambiguates the ambiguous identifier semantics per queue type. It also names the underlying endpoint, so an agent can distinguish this from delete_media at a glance.

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 line 'The media file itself is not deleted' implicitly routes the agent away from delete_media, and 'Queue changes can affect live output' signals the operational context. But it never explicitly states when to use this versus skip_stream_queue or play_stream_queue_item, nor any prerequisites, so 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.