List PCB tracks

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

Annotations already declare readOnlyHint and idempotentHint, so the description's main added value is the focus requirement and the explicit failure behavior: mismatched or missing focus returns not_available rather than an empty list. That is meaningful behavioral context beyond annotations, though pagination behavior is not described.

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 tightly written sentences, with the main purpose front-loaded and the focus/error condition immediately after. No filler or repetition.

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?

The tool has an output schema and annotations covering safety, so the description does not need return-value details. It covers the critical project/PBC focus precondition and the not_available error case; the remaining gap is pagination semantics for limit/offset, which is partially constrained by the schema.

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 only 33%: projectId is documented in the schema, while limit and offset have only type/default/min/max constraints. The description reinforces 'exact active project UUID' but does not explain what limit/offset do or how pagination works, so it does not compensate for the undocumented pagination parameters.

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: list native copper track segments plus net/layer geometry. This distinguishes it from PCB siblings like pcb_vias, pcb_fills, and pcb_regions by naming 'track segments', though it doesn't explicitly call out the sibling alternatives.

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?

Gives an important precondition: the exact active project UUID and focused PCB are required. However, it does not say when to prefer this over sibling PCB listing tools such as easyeda_pcb_vias or easyeda_pcb_regions, so usage relative to alternatives is only implied.

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