Prepare PCB copper zone or keepout mutation

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

The annotations declare readOnlyHint=true and destructiveHint=false, so the safety bar is lower, yet the description still adds real value by explaining why: the tool only stages a preview and generates a confirmation phrase, and 'Does not modify the PCB until confirmed' resolves the apparent tension between a delete/rebuild capability and a read-only hint. It stops short of describing what the preview contains or where the phrase is submitted.

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?

Two short sentences, front-loaded with the scope and ending with the key safety constraint. The first sentence is dense but every clause carries information; there is no filler.

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 17-parameter mutation tool with a nested target object and no output schema, the description leaves important gaps: the mechanics of the two-phase confirm flow, what the preview returns, and how parameters map to actions are all unstated. It is minimally adequate but not complete for the tool's complexity.

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 94%, so 16 of 17 parameters are already documented in the schema, giving a baseline of 3. The description adds no parameter-level meaning at all, notably omitting which parameters are required per action/entity combination (e.g. zoneId for modify/delete vs points/x/y/width/height for create).

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 names a specific verb (prepares) plus the exact resources (copper zones and keepouts) and enumerates the four staged actions (create, modify, delete, rebuild) on the active PCB canvas. That is enough to distinguish it from read-only siblings like easyeda_get_copper_zones and easyeda_get_keepouts, though it never names the tool that actually commits the change.

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 only implied: 'with safety preview and exact confirmation phrase' hints at a two-phase flow, but the description never states that the agent must follow up with easyeda_confirmed_action, nor when to prefer this over easyeda_get_copper_zones / easyeda_get_keepouts for inspection. No explicit when-not or alternative routing is given.

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