simulate_subcircuits

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does reveal a meaningful conditional ('run them if a simulator is present') and the comparison step, but it does not mention side effects such as writing testbench files, whether results are returned or persisted, or what happens when no simulator is present. This leaves uncertainty about a potentially mutating operation.

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 dense sentence that front-loads the main action and avoids filler. However, it packs three workflow steps into one clause string, leaving no room for usage caveats or parameter context. It is appropriately concise but slightly too compressed for the tool's complexity.

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 tool with four parameters, no annotations, and a multi-step behavior, the description is materially incomplete. It omits parameter meanings, simulator prerequisites, behavior when run=false or tolerance_pct is set, and any routing guidance among close sibling tools. The presence of an output schema helps return-value understanding but cannot compensate for the missing operational context.

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 0%, yet the description does not explain any of the four parameters. schematic_path, run, tolerance_pct, and follow_hierarchy are all undocumented in both the schema and the description, so an agent cannot reliably know how to set them. The only vague connection is the phrase 'run them,' which hints at the run flag but does not clarify its semantics.

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 a clear verb-resource relationship: generate.SPICE testbenches, run them, and compare against analytical values. It conveys a specific workflow that goes beyond a generic label, though it does not explicitly name sibling tools to distinguish itself from run_spice or export_spice_netlist.

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 when-to-use or when-not-to-use guidance is provided. It does not say when to choose this over run_spice, export_spice_netlist, or veriy_netlist, and it does not mention any prerequisites or exclusions. The only implicit signal is that it operates on 'subcircuits the detectors found.'

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