pattern_jump_to_previous

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

The description discloses the core side effect: changing the selected pattern to the previous one. However, with no annotations and no output schema, it leaves meaningful behavioral traits undisclosed, such as wrap-around behavior, behavior at the first pattern, and whether the call returns any value.

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 short sentence with no filler or repetition. The action is front-loaded, and every word contributes to the meaning.

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 parameterless navigation command with no output schema, the description states the essential behavior well enough for an agent to decide to call it. The main gaps are boundary behavior and return expectations, but the low complexity makes the description largely sufficient.

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 has zero parameters, and the empty input schema documents that completely. Since there are no parameters to explain, the description does not need to add parameter-level detail, so the parameterless baseline of 4 applies.

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 states a clear action — 'Select the previous pattern in the list' — with a specific verb and resource. However, it does not explicitly distinguish itself from pattern_jump_to_next or explain what 'the list' refers to, so it is clear but not fully differentiated.

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 about when to use this tool versus alternatives like pattern_select, pattern_list, or pattern_jump_to_next. There is also no mention of prerequisites such as having a current pattern selected or what happens at the beginning of the list.

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