The swap queue

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

The description hints at behavior (empty queue causing auto-swap to do nothing) but does not disclose whether the operation is read-only, if it has side effects, or what it returns. The absence of annotations increases the need for such disclosure.

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?

The description is verbose and redundant, repeating the same idea in both sentences ('lined up to go live' and 'where rotation gets its replacements'). It could be condensed into one clear sentence.

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?

The description does not explain what the tool returns (e.g., a list of thumbnails, metadata) or any error conditions. Given there is no output schema, the description should fill that gap but fails to do so.

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?

The parameter 'game' is documented in the schema with a clear description. The tool description adds no additional meaning or context about how the parameter affects the queue retrieval, so it does not enhance the schema.

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 explains what a queue is but does not clearly state that the tool retrieves the queue. It says 'Thumbnails lined up to go live' rather than 'This tool gets the queue of thumbnails', so the purpose is implicit rather than explicit.

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?

No guidance is given on when to use this tool versus alternatives like queue_thumbnail or get_auto_swap. The description does not mention any specific scenarios or user intentions.

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