Set native pin No Connect state

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

Annotations already supply readOnlyHint=false and idempotentHint=true, so safety and repeatability are covered. The description adds genuinely useful behavior beyond that: the bridge rejects missing/ambiguous pins and verifies native readback after the write, plus the explicit note that it mutates noConnected rather than creating connectivity.

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?

Three sentences, all front-loaded with the operation and scope first, then the negative disambiguation, then the validation behavior. Every sentence earns its place with no repetition of the name or schema.

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?

With an output schema present (return values need not be explained), full schema coverage, and annotations covering safety and idempotency, the description is complete: it covers purpose, disambiguation, mutation scope, and rejection/readback 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?

Schema description coverage is 100%, so the schema already documents all five parameters (including confirmWrite's literal-true requirement and the noConnected default), which sets the baseline at 3. The description confirms the single-pin granularity but adds no syntax or format detail beyond the schema.

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 pair ('set or clear') and precise resource ('native No Connect marker on one exact component pin'), then explicitly rules out what it is not (net, label, power flag, short-circuit flag), which separates it from siblings like easyeda_schematic_create_net_flag and easyeda_schematic_connect_pin_to_net without opening their schemas.

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 single-pin scope and the negative disambiguation ('does not create a net, label, power flag, or short-circuit flag') tell the agent when this tool is the right choice versus sibling flag/connect tools. It stops short of naming an explicit alternative or stating a when-not condition, so it is clear context rather than full routing guidance.

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