eda_lib_device_create

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

The description discloses that the tool creates a device and returns a Promise resolving to a device UUID or undefined. However, with no annotations available, it omits important behavioral details such as failure semantics, prerequisite conditions, duplicate-name behavior, or what 'undefined' means.

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 compact and free of filler, consisting of the signature, a concise Chinese summary, and the return value. The signature is long due to nested types, but each component is informative and no words are wasted.

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 complex create operation with no annotations and no output schema, the description is incomplete. It provides no examples, no guidance on how to obtain a valid libraryUuid or construct classification/association/property values, and no explanation of failure or duplicate behavior, leaving an agent to infer too much from types alone.

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 only exposes an opaque args array, so the full TypeScript signature in the description is the primary source of parameter meaning. It provides parameter names, order, optionality, and nested structures like association, which is essential for constructing correct arguments, though it does not explain enum values or semantic details of each field.

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 identifies the operation as creating a device ('创建器件') and the first line is an explicit API signature for lib_Device.create. It is distinguishable from sibling device tools like eda_lib_device_modify or eda_lib_device_search by the verb and resource, though it does not explicitly name those 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?

There is no guidance on when to use this tool versus alternatives. The description only states that it creates a device, but an agent is not told what context warrants creation, what prerequisites exist, or why it would be preferred over other device-related operations.

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