create_circuit

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

The description confirms a write operation (store), consistent with readOnlyHint=false. However, it does not disclose behaviors beyond what annotations already imply, such as error handling, validation, or the meaning of 'store' (e.g., does it overwrite existing circuits?).

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 with no waste. It efficiently communicates the core purpose.

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?

The description covers the main function but lacks details about the optional 'models' parameter and edge cases. For a tool with no output schema, it could mention the return format or error conditions.

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?

With 0% schema description coverage, the description should compensate but does not. It mentions 'netlist' implicitly but does not describe the 'models' parameter or provide any context about parameter formats or constraints.

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 uses a specific verb 'Store' and resource 'SPICE netlist', clearly stating the outcome 'return a circuit ID for subsequent analyses'. This differentiates it from siblings like delete_circuit and create_model.

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 guidance is provided on when to use this tool versus alternatives (e.g., when to use create_circuit vs load_template or validate_netlist). No prerequisites or exclusions are mentioned.

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