open_generation_queue

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

With no annotations, the description must carry the full behavioral burden, and it does disclose that the target is a *local* dashboard whose controls include preview, pause, resume, and cancel. It does not say what the call returns (a URL? a launched browser?), whether it has side effects on the host, or what happens in headless/no-display environments — meaningful gaps for a UI-launching tool.

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?

A single front-loaded sentence with the action, target, and capability set, and no wasted words. It is exactly as long as the information it conveys.

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 no-parameter, no-output-schema tool, the description covers what it does and roughly what the agent/user will find there. The only real omission is the return value and the side effect of launching a local UI, which is modest given the tool's simplicity.

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 tool takes zero parameters, so the schema needs no compensation and the baseline of 4 applies. Nothing in the description misrepresents the parameter surface.

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?

A specific verb ("Open") plus a specific resource ("local queue dashboard") tells the agent exactly what happens, and the phrase "previews and pause/resume/cancel controls" signals this is a UI surface rather than the programmatic controls in siblings like pause_generation_batch or cancel_generation. It stops short of naming any sibling outright, so differentiation 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?

Usage is only implied: an agent can infer this is for when a human wants to view and manipulate the queue visually, while get_queue_status or pause_generation_batch are the machine-facing equivalents. There is no explicit when-to-use, when-not-to-use, or named alternative.

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