eda_pcb_net_set_netlist

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It fails to mention side effects, return value meaning (Promise<boolean> is not explained), permission requirements, or whether the operation is reversible. The agent has no idea what happens when this is called.

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 brief (one signature and a two-character phrase), but it is under-specified rather than efficiently concise. It lacks any natural-language explanation or structuring that would help an agent parse key information.

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 tool with no output schema, no annotations, and minimal parameter documentation, this description is wholly inadequate. An agent cannot determine how to construct valid inputs, what success looks like, or what preconditions apply.

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 signature lists types (ESYS_NetlistType, string) but provides no explanation of what 'type' values are valid, what format 'netlist' should be in, or what the arguments mean in context. The schema only defines an 'args' array without item descriptions, so the parameters are effectively undocumented.

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 'update netlist' which is essentially a translation of the tool name. It gives a verb and resource but no detail on what 'update' entails, what netlist types exist, or how it differs from schematic netlist tools. The signature line adds parameter names but no semantics.

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 like eda_pcb_net_get_netlist or eda_sch_netlist_set_netlist. No context about required document state, prerequisites, or exclusions.

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