eda_pcb_primitive_attribute_delete

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the return type (boolean) and that it deletes an attribute, but does not mention side effects, failure conditions, whether deletion is irreversible, or any error handling. The name implies destructiveness but no details are given.

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 very short (a signature and two short Chinese phrases), which is concise, but it lacks structure or front-loading of key information. It is under-specified rather than efficiently concise; it reads like a raw API dump rather than a purpose-written description.

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 simple delete operation, the description is still incomplete. It does not explain what an attribute is, how to target it, what the boolean return value means beyond success/failure, or any error conditions. With no output schema and minimal behavioral info, an agent would struggle to know if the call succeeded or why it failed.

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 a type signature listing primitiveIds and its accepted types, but it does not explain what an IPCB_PrimitiveAttribute is, how to obtain primitiveIds, or how to structure the args array per the schema. The schema itself only describes args as a generic JSON array, so the description adds minimal practical meaning for invoking the tool correctly.

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 names the operation 'delete attribute' and provides the function signature, making it clear this tool deletes a primitive attribute on a PCB. It distinguishes from siblings like create/get/modify by the verb 'delete', though it does not explain what an attribute is or what effect deletion has beyond the name.

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 when an attribute should be deleted, any prerequisites (e.g., existence of the primitive), or scenarios where deletion is inappropriate. The description is purely declarative and offers no contextual routing.

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