plugin_next_preset

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

No annotations are provided, and the description only says 'advance', implying a state change but not disclosing effects, edge cases such as wrapping at the last preset, or failure behavior. The description carries the full burden here and does not satisfy it.

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 concise sentence with no filler, and the verb is front-loaded. It is appropriately brief, though the brevity contributes to the lack of context.

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 three parameters, no annotations, and no output schema, this description is far from complete. It does not explain target selection, parameter usage, or relationship to sibling preset tools, so an agent cannot reliably construct a correct call.

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 description coverage is 0%, and the description adds no meaning to the parameters slot, index, or location. An agent cannot tell why index is required, what slot=-1 means, or how location changes the behavior.

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?

'Advance to the next preset' clearly states the action and resource, and the direction distinguishes it from sibling plugin_prev_preset. However, it does not specify which plugin or preset context is being advanced (channel vs mixer, slot vs index), leaving some ambiguity.

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 about when to use this tool instead of plugin_prev_preset, plugin_set_preset, or plugin_find_param. There is no context for typical workflows or prerequisites, so an agent must infer usage purely from the name.

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