Get PCB tracks

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add value by naming the returned attributes (net, layer, geometry coordinates, width, calculated length), which matters since there is no output schema. It omits the limit default of 100 / cap of 500 and any truncation behavior, which is the main gap.

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 resource and scope come first, followed by the fields inspected. Slightly list-like but every clause carries information.

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 7-parameter, zero-required read tool with a nested target object and no output schema, the description covers purpose and returned fields but leaves filter interplay, default paging and truncation unstated. Adequate but with clear gaps.

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 71%, with net, layer, limit, includeRaw and primitiveId all documented in the schema itself, so baseline 3 applies. The description adds nothing about parameters, and the two undocumented fields (target and timeoutMs) receive no explanation here either.

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?

Concrete verb plus resource: 'Lists and inspects copper tracks and traces on the active PCB layout.' That cleanly separates it from nearby PCB readers such as easyeda_get_pcb_vias, easyeda_get_pcb_pads and easyeda_get_copper_zones, though it never names those siblings explicitly.

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 only usage cue is 'on the active PCB layout', which implies a PCB context but says nothing about when to pick this over easyeda_get_routing_status, easyeda_get_pcb_net_report or easyeda_trace_net. No when-not conditions, no mention of how the net/layer filters should be used for targeted inspection.

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