Skip Image

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

With no annotations, the description must carry the full burden. It states the behavior of skipping the current image but does not disclose consequences such as whether the generation job is canceled, how the queue advances, or idempotency. For a simple tool, this is acceptable but not rich; it leaves some potential side effects underspecified.

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 a single sentence that directly communicates the purpose and endpoint, with no verbose or redundant content. It is perfectly concise and front-loaded, minimizing cognitive load.

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?

Given the tool's simplicity (no params, no output schema, no annotations), the description is essentially complete. It names the action and the endpoint. However, it could mention edge cases (e.g., behavior when no image is in queue) or side effects more explicitly, but this is not strictly necessary for a straightforward skip operation.

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 per the rubric, the baseline is 4. The input schema is empty, and the description adds no parameter info because there is nothing to add. Since there are no parameters, the description adequately covers semantics without needing further detail.

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 clearly states the tool's action: skipping the current image in the queue, and includes the specific endpoint. This is a distinct verb+resource that differentiates it from siblings like sdnext_interrupt (which halts generation) or sdnext_restart, making purpose immediately clear.

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 description explains exactly what the tool does, so when to use it is self-evident. However, it does not explicitly mention when not to use it or provide alternatives, though given the simplicity and uniqueness of 'skip', this omission is minor. The context is clear enough for a one-shot action.

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