flip_pattern

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

With no annotations, the description carries the behavioral disclosure burden. It does state that the operation flips a pattern piece and exactly how the boolean maps to horizontal/vertical behavior. However, it does not explicitly say whether the piece is modified in place, whether the flip is reversible, or what the tool returns, leaving some side-effect ambiguity.

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 compact and front-loaded: one clear action sentence followed by a minimal Args block. There is no filler, and every line adds useful semantic information.

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 simple two-parameter operation, the description is mostly adequate to make a valid call. It is incomplete, though, because it does not clarify side effects or distinguish flip_pattern from the overlapping sibling mirror_pattern, and there is no output schema to clarify the return behavior.

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 schema has 0% description coverage, but the description fully compensates by explaining that pattern_index is zero-based and that horizontal=true means horizontal flip while horizontal=false means vertical flip. Both parameters receive meaningful semantics beyond their raw names and types.

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 a specific action ('flip'), a specific target ('a pattern piece'), and the two supported orientations ('horizontally or vertically'). It is clear and distinguishable from most siblings, but it does not explicitly differentiate itself from the similarly named mirror_pattern sibling.

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 gives no guidance on when to use flip_pattern versus alternatives such as mirror_pattern, move_pattern_2d, or copy_pattern. It also provides no exclusions or conditions, so the agent must infer the appropriate usage context.

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