Queue a thumbnail

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

With no annotations, the description carries the burden and does well: it discloses that queuing does not change what players see, that auto-swap promotes later, and that set_active_thumbnails bypasses the queue. It could also mention queue ordering/replacement or cancellation, but the core behavior is transparent.

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 sentences, front-loaded with the purpose, followed by a prerequisite and behavioral caveat. Every sentence earns its place with no filler or redundancy.

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 simple two-parameter tool with no output schema, the description is complete: it explains what the tool does, what must happen first, what effect it has on players, and how to achieve immediate activation. The presence of sibling tools like unqueue_thumbnail and get_queue makes the surrounding context even richer.

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. The description adds extra meaning by clarifying the id parameter must reference an existing thumbnail already uploaded to the game, which supplements the schema's 'Asset id or thumbnail id from get_thumbnails'.

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 names a specific action (queue an existing thumbnail) and a clear resource scope (existing thumbnails already on the game). It distinguishes itself from siblings by explicitly contrasting queuing with set_active_thumbnails and auto-swap behavior.

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 states the prerequisite explicitly (the thumbnail must already be on the game; upload it first if not), and provides an alternative path (set_active_thumbnails for immediate live placement). This gives the agent clear when-to-use and when-not-to-use guidance.

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