pcb_create_via

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether the via is created on all layers, whether it requires authentication, or if it modifies existing data. The description is entirely opaque regarding side effects or constraints.

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 extremely short (one phrase), which is concise but fails to provide sufficient information for an agent to understand the tool's function. It lacks structure and does not use front-loading effectively. The brevity results in under-specification.

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?

Given the absence of annotations and output schema, the description is critically incomplete. It does not explain what a via is, how coordinates are interpreted, or the outcome of the operation. The schema descriptions partially compensate, but the tool description itself leaves significant 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?

The input schema has 100% coverage, with each parameter given a brief description in Chinese (e.g., '网络名称' for net). The tool description does not add any additional context or meaning beyond what the schema already provides. Baseline score of 3 is appropriate.

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 '创建过孔' (Create via) states the basic action and object, but does not add any detail beyond the tool's name. It is not vague, but it is essentially tautological and does not distinguish the tool from siblings like pcb_delete_via. The purpose is clear but minimally communicated.

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 guidance on when to use this tool versus alternatives. No mention of context, prerequisites, or when not to use it. Sibling tools exist for creating other objects (e.g., pcb_create_component), but the description provides no direction.

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