Verify symbol pin to footprint pad correspondence

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine value by naming what is detected (unmapped pins, unmapped pads, netlist breaks), but it says nothing about the reporting behavior implied by idempotentHint=false or about how results are returned, so the extra context is moderate rather than rich.

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 core validation action and followed by the concrete diagnostics produced. No filler, though the second sentence could be folded in for tighter structure.

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 no output schema and a nested target object among four parameters, the description does the minimum: it names the checks performed. It omits output shape, how failures vs passes are reported, and what the timeout and target object mean, so an agent can select the tool but not fully predict its response.

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 50%: designator and deviceUuid are documented in the schema itself, so the description's scope note ('active canvas or for a specific component') largely repeats them. The opaque nested target object and timeoutMs are undocumented in both places, and the description does not explain their role, so it does not fully compensate for the coverage gap.

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: 'Validates 1-to-1 correspondence between schematic symbol pins and PCB footprint pads', with scoping to the active canvas or a specific component. It is clear what the tool does, but it never names close siblings such as easyeda_compare_schematic_pcb, easyeda_verify_connections, or easyeda_find_unconnected_pins, even though its stated outputs (unmapped pins, connectivity breaks) overlap those tools.

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 description implies when to use it — when you want to check pin/pad mapping integrity — and the schema's designator parameter's description explains scope widening to all components. But there is no explicit when-not guidance and no routing to the overlapping verification siblings, leaving the agent to infer which verification tool to pick.

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