eda_pcb_primitive_fill_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 of behavioral disclosure. The description only says 'create fill' (创建填充) and mentions a return value, but does not disclose mutating behavior, whether a board/document must be open, whether the operation is reversible, how the fill is inserted, or any side effects. The signature does show it returns a Promise<IPCB_PrimitiveFill | undefined>, but the description adds no behavioral context beyond that.

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 short and front-loaded with the callable signature, then a short Chinese description '创建填充' and a returns line. It is not bloated, but the Chinese description is duplicative of the English signature and the returns line is minimal. It earns a pass for brevity, but the structure mixes a raw API signature with a terse one-liner rather than a coherent, helpful explanation.

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 creation tool with no annotations and no output schema, the description is insufficiently complete. It omits required context such as how to obtain the IPCB_Polygon input, what layers are valid for TPCB_LayersOfFill, how the fill relates to copper pours or regions, and what 'undefined' in the return means. The agent would struggle to construct a correct invocation despite the listed parameter types.

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?

Schema description coverage is 100% for the two top-level parameters (args and windowId), but the args array items are untyped (items: {}), so the actual function parameters are not documented in the schema. The description's signature lists parameter names and types, which adds meaning beyond the empty items schema. However, it does not explain semantics like what fillMode values mean, what lineWidth units are, or what primitiveLock does, leaving the agent without real understanding of the arguments.

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 the verb 'create' and the resource 'fill' (填充), plus a closing '创建填充' which means 'create fill'. This identifies a PCB primitive fill creation operation. However, it doesn't explicitly differentiate from sibling tools like eda_pcb_primitive_pour_create, eda_pcb_primitive_region_create, or eda_pcb_primitive_fill_modify, leaving the agent to infer the specific fill-type distinction.

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 provides no guidance on when to use this tool versus alternatives such as pour_create, region_create, or fill_modify. There is no mention of prerequisites (e.g., needing a polygon or a target layer), no context about whether this is for copper fills, no exclusions, and no hints about when a fill is preferred over a pour or region.

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