eda_sch_primitive_bus_create

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

No annotations are provided, so the description carries the full burden. It only provides a function signature and a terse statement that it creates a bus. It does not disclose side effects, error conditions, undo behavior, or any operational context beyond the signature.

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 concise, consisting of a signature and two short phrases, but it lacks structure such as separate sections for description, parameters, and returns. It is not bloated, but it is also not well-organized.

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 is highly incomplete for a create operation. It does not explain the meaning of parameters (e.g., what 'line' represents), the coordinate system, allowed values for ESCH_PrimitiveLineType, or any requirements like an active document. There is no output schema, so the return type '总线图元对象' is too vague to convey the object structure.

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 supplies the full parameter list with names, types, and optionality (busName, line, color, lineWidth, lineType), which is not present in the input schema that only defines a generic 'args' array. This is essential for an agent to construct correct calls.

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 clearly states the tool creates a bus primitive ('创建总线'), with a specific resource and action. It distinguishes from other primitive create tools by name and signature, though it does not explicitly contrast with siblings like eda_sch_primitive_arc_create or eda_sch_primitive_circle_create.

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 prerequisites, such as needing an active schematic document, or situations where this tool is preferred over other primitive creation tools.

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