pcb_netlist_report

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

No annotations are provided, and the description only says it generates a report. It does not explicitly state that it is read-only, whether it modifies any PCB data, or what the output format looks like. For an unannotated tool, this leaves behavioral expectations unclear.

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 a single, front-loaded sentence that efficiently conveys the purpose and scope without redundant words. Every word contributes to understanding, and it avoids unnecessary length.

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 read-only report tool with no parameters, the description covers the core functionality but lacks specifics about the report's output format, structure, or usage context. Without an output schema, the agent must infer what the report returns. The description could be more complete by stating the expected output type or typical use cases.

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?

This tool has zero parameters, so the baseline of 4 is appropriate. The description's mention of 'from PCB pad data' implies the source input, though no further parameter details are needed. It adds meaning beyond the empty schema by explaining the data source.

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 states the verb 'generate' and the resource 'netlist report from PCB pad data', specifying the direction (component→pin→net and net→component). This distinguishes it from sibling report tools like pcb_bom_export or pcb_design_health_report by focusing on netlist content.

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 sch_get_netlist or pcb_get_net_primitives. It fails to mention prerequisites, use cases, or exclusions, which is essential for a reporting tool among many.

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