run_sweep

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

Describes internal use of SimRunner, concurrency, per-run .npz file creation, and default parallelism. Mentions output format (JSON list with run, data_file, values, traces). No annotations provided, so description fully carries the burden.

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?

Well-organized: purpose sentence, implementation detail, usage recommendation, example, parameter descriptions, return description. Every sentence adds value; no redundancy.

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?

Covers all inputs and output format despite having output schema. Explains output file naming and return structure. Even with good annotations, the description would be complete; without annotations, it is exemplary.

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?

All four parameters are explained with descriptions, types, and examples. netlist_path as absolute path, analysis_cmd as full SPICE line, runs as list of dicts with key-value pairs, parallel with default. Compensates for 0% schema description coverage.

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?

Clearly states it runs multiple SPICE simulations in parallel sweeping component values. Distinguishes from siblings by explicitly advising use instead of calling run_ac_analysis/run_transient in a loop.

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 tells when to use this tool vs alternatives: 'Use this instead of calling run_ac_analysis / run_transient in a loop — it's significantly faster for multi-run sweeps.' Provides a concrete example.

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