Run semantic ERC validation

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the detection scope (contention, floating inputs, power conflicts, decoupling, voltage-domain mismatches), which is genuinely useful behavioral context, but says nothing about the input being required to be complete or what happens on malformed nets.

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?

A single front-loaded sentence with no filler; the purpose verb comes first and the check list follows. The enumeration is long but each item is a distinct detection capability, so it earns 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?

An output schema exists, so return values need not be described, but for a 4-parameter tool with deeply nested net/device/interface objects and 0% schema coverage the description is far too thin. It never explains what input completeness is required nor how the three optional collections interact.

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% across all 4 parameters, so the description carries the burden — yet it only vaguely gestures at 'a netlist with pin electrical types'. The roles of devices, interfaces, and projectId, and which fields drive each check, are never explained in text.

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 ('semantic electrical-rule validation over a netlist') and enumerates the exact defect classes it detects, which is far more informative than a tautology. It does not, however, distinguish itself from close siblings like easyeda_erc_run or easyeda_semantic_erc_auto, so an agent must still guess which of the three ERC-family tools applies.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the alternatives in a sibling list containing at least three ERC-related tools (easyeda_erc_run, easyeda_semantic_erc_auto, easyeda_schematic_validate_netlist). The reader is left to infer usage entirely from the purpose sentence.

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