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

With destructiveHint=false already declared, the description still adds real substance: exactly which attributes survive, that nets are remapped pad by pad, that schematic Footprint fields are rewritten, and that the result reports unconnected new pads and orphaned old nets. It stops short of stating permissions, reversibility/undo, or failure modes on a bad library reference.

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 critical information (in-place replacement, preserved attributes, net remapping) is front-loaded in the first clause. The first sentence is clause-heavy and slightly run-on, but every clause carries operational meaning — no filler sentences.

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?

No output schema exists, and the description covers what matters: it states the tool reports new pads without nets and old nets left behind, and the schema documents design_id and the job/wait_s polling flow. Batch limits and per-swap failure handling are left implicit, keeping it just under complete.

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 coverage is 67%, yet the description supplies the missing semantics for pad_map — 'maps a NEW pad number to the OLD pad whose net it takes' — and clarifies the 'library:name' format the footprint pattern encodes, plus the rot_deg/pad_map interaction. It does not explain refs cardinality or the swaps-array structure, so it is not a full 5.

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 ('Replace footprints in place with another footprint from a library') plus the source of the new footprint (fp-lib-table). An agent can distinguish this from siblings like place_footprints, add_custom_footprint, and search_kicad_footprint without opening a schema.

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?

Gives clear context for when this is the right operation: preserving reference, value, position, rotation, side, lock and schematic link while moving nets pad by pad, and using pad_map when packages are numbered differently. There is no explicit 'use X instead' routing to the neighbouring footprint tools, so it falls short of 5.

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