pcb_flip_component

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the mutation and the returned fields but says nothing about whether attached copper, silkscreen, or 3D bodies flip with the part, whether the action is undoable, whether internal layers are valid targets on multilayer boards, or what happens if the designator is unknown.

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?

One front-loaded sentence conveys the operation and its direction; the Args line adds only the needed parameter example. The Returns line is mild redundancy given an output schema exists, but it is short enough to earn its place.

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 single-parameter mutation tool with no annotations, the definition covers what it does and what it returns, but leaves the side-effect profile unspecified. An agent could call it correctly, yet not confidently predict the consequences for attached routing or footprint primitives.

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%, so the description must compensate — and it does, naming the designator parameter and giving concrete examples ('U1', 'R5'). It stops short of stating the expected format constraints (case sensitivity, prefix+number pattern) or error behavior for a bad designator.

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?

States a specific verb and resource — flip a component to the other board side — and clarifies the direction (top↔bottom). It distinguishes itself from the move-oriented siblings (pcb_move_components, lib_move_components) by naming a distinct operation, though it never explicitly contrasts with them or with sch_mirror_component.

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?

Usage is implied by the operation itself: use it when a part must be relocated to the opposite side. There is no explicit when-to-use/when-not statement, no prerequisite (e.g., component must exist in the PCB, board must have a defined stackup), and no pointer to alternatives for other kinds of relocation.

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