eda_sch_primitive_wire_create

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that it creates a wire and returns an object, but does not mention side effects, required conditions, failure behavior, or any mutation implications. This is minimal disclosure for a creation tool.

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 brief and to the point: a signature and two short Chinese phrases. It avoids unnecessary words and is well-structured, though it could have used the space to include usage context.

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 description lacks important context such as the format of the `line` parameter (coordinate system, units), the target window/document requirements, and any constraints or defaults. For a creation tool with no output schema, this is incomplete for correct invocation.

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 description includes the full function signature with parameter names and types (line, net, color, lineWidth, lineType), which adds meaning beyond the generic `args` array in the schema. This gives an agent the correct parameter order and types, which is helpful despite the schema coverage being 100%.

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 states '创建导线' (create wire) and includes the function signature, clearly indicating it creates a wire primitive. The name also unambiguously denotes a create operation, and it is differentiated from sibling get/modify/delete wire tools by its verb and resource, though it doesn't explicitly mention 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?

No guidance is given on when to use this tool versus alternatives such as modify or delete, and no prerequisites (e.g., active schematic document) are mentioned. The description lacks any context that would help an agent decide when to invoke it.

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