Prepare Schematic Port Mutation

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

The annotations only say readOnlyHint=true and destructiveHint=false; the description adds the crucial context that this call stages a mutation, produces a preview plus validation, and emits an exact confirmation phrase that must be echoed to easyeda_confirmed_action. That reconciles the seemingly odd readOnlyHint on a create/modify/delete tool and prevents the agent from assuming the change already happened. It leaves idempotentHint=false unexplained (whether repeated calls stack duplicate previews) and says nothing about how long a prepared action stays valid.

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 sentences, front-loaded with the operation and resource, then the non-obvious staging/confirmation constraint. Every clause carries information an agent needs; nothing is redundant with the title or annotations.

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 10-parameter tool with a nested target object and no output schema, the description never indicates what the preview/validation result contains, where the exact confirmation phrase comes from, or what happens on validation failure. It is adequate to identify and invoke the tool but leaves the agent guessing about the result and the confirmation handshake details.

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?

With 90% schema description coverage, the schema already documents the action enum, portId, portType, rotation, coordinates, and the nested target object, so the baseline applies. The description adds no parameter-level meaning beyond the schema — for example, that portId is required for modify/delete but ignored for create, or which fields the validation checks against target.

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) and precise resource (schematic net port / hierarchical sheet connector) and enumerates the three operations it stages (create, modify, delete). The resource noun alone distinguishes it from siblings such as easyeda_prepare_schematic_wire, _bus, and _component, so no schema look-up is needed to tell them apart.

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?

It explicitly states the follow-up path: nothing is written until confirmed via easyeda_confirmed_action, which tells the agent this is a staging step rather than a standalone mutation. It does not, however, say when to choose this over the sibling prepare_* tools, nor whether a preview can be discarded or must be confirmed.

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