Generate Netlist

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces with 'Does not write any file.' It also discloses that the return is a structured JSON object, adding useful behavior context beyond the annotations. No contradiction, so the score reflects the extra value added.

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?

Three sentences, each earning its place: purpose, usage, and alternative. Front-loaded with the core action and immediately clarifies what the output contains and why to use it. No filler or repetition of schema/annotations.

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 tool with one parameter and an output schema, the description explains the return structure sufficiently (component list and net list) and clarifies side-effect-free behavior. It also points to the export alternative, making the tool's place in the broader workflow clear.

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 single parameter schematicPath, so the schema already defines it. The description only mentions 'from the schematic' contextually, adding no extra parameter-level meaning. Baseline 3 is appropriate when the schema carries the semantic load.

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 opens with a specific verb and resource: 'Return a structured JSON netlist from the schematic' and explicitly names the output contents (component list and net list). It distinguishes itself from the sibling export_netlist tool by contrasting its in-conversation JSON return with file export.

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?

Explicitly states when to use it ('to inspect or verify connectivity within the conversation') and points to the alternative tool 'export_netlist' for file export in specific formats. This gives clear usage direction and differentiates it from the closest sibling.

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