pcb_get_net_primitives

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

There are no annotations, so the description carries the full burden. 'Query' implies a read-only operation, but the description does not disclose the return shape, whether all primitive types are included, or what happens for an unknown or empty net.

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?

The description is a single, front-loaded sentence with no filler. Every word contributes to stating what the tool returns.

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 single-parameter query this is minimally viable: an agent knows what to supply and what kind of data comes back ('all primitives'). However, there is no output schema or description of the return format, so the agent cannot predict the response structure or error 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 coverage is 100%: the only parameter 'net' is already documented as '网络名称' (net name). The description only restates this by referring to the 'specified net' and adds no format, validation, or default information.

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?

The description uses a specific verb ('query') and a precise resource ('all primitives of the specified net'), making the operation unambiguous. This distinguishes it from sibling getters like pcb_get_tracks and pcb_get_pads, which filter by primitive type rather than by net.

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?

No guidance is given on when to choose this tool instead of related retrieval tools such as pcb_get_tracks, pcb_get_pads, or pcb_get_silkscreens. The agent must infer the appropriate context from the tool name alone.

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