Delete Trace

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows it is a destructive write operation. The description adds the mode-of-deletion info (UUID/position/bulk) but that is already present in the schema; it does not disclose side effects like whether vias are removed by default or whether deletion is permanent beyond the annotation.

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 two short sentences, front-loaded with the primary action. No unnecessary words; each clause adds relevant information about the deletion modes.

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?

Given the rich schema and annotations, the description adequately orients the agent, but it omits the includeVias nuance and the precise meaning of position-based deletion beyond what schema states. The tool appears simple and safe to understand with the structured data, so the description is sufficient but not exhaustive.

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 schema has 100% parameter coverage, describing each parameter's purpose. The description merely summarises the three deletion methods (UUID, position, net) without adding new details about units, defaults, or interactions between parameters.

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 uses a specific verb ('Delete') and resource ('traces from the PCB'), and clearly identifies three deletion modes (UUID, position, bulk net). It distinguishes from sibling tools like modify_trace and route_trace by focusing on removal rather than modification or creation.

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?

The description implies when to use the tool (to remove traces) but provides no explicit guidance on alternatives or when not to use it. Sibling tools like query_traces and modify_trace are not mentioned, leaving the agent to infer the appropriate context.

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