plugin_next_preset

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

With no annotations and a minimal description, the tool fails to disclose behavioral traits such as whether advancing wraps around, what happens if no next preset exists, or any side effects. The agent is left uninformed.

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 extremely short (one phrase), but under-specification makes it unhelpful. Conciseness at the cost of missing critical information is not a virtue.

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 lack of schema descriptions, output schema, and annotations, the tool description is completely inadequate. It does not explain required parameters, expected behavior, or return values, leaving the agent without sufficient context to use the tool correctly.

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 input schema has three parameters (index, slot, location) with 0% description coverage, and the tool description provides no explanation of their meaning or effect. The agent has no guidance on how to fill them correctly.

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 'Advance to the next preset.' is essentially a tautology of the tool name 'plugin_next_preset', repeating the same concept without adding specificity. It does not distinguish from sibling tools like 'plugin_prev_preset' beyond the direction.

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 provided on when to use this tool versus alternatives such as 'plugin_prev_preset' or 'plugin_set_preset'. The description lacks context for appropriate usage.

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