cst_parameter_sweep

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

No annotations provided, so the description must fully disclose behavioral traits. It states the sweep runs simulations multiple times, but does not clarify whether it both sets up and executes, whether it modifies project state, or how results are returned. It lacks details on side effects, asynchronous execution, or required prior setup.

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 two sentences, front-loaded with the core purpose, and contains no redundant information. It is appropriately sized 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 that sets up and runs simulations, the description omits crucial details: whether execution is synchronous, how to retrieve results, and what the output format is. Since no output schema exists, the description should provide more context on return values or side effects.

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 coverage is 100% with descriptions for each parameter. The tool description adds no significant meaning beyond the schema; it does not explain step type (e.g., linear/logarithmic) or constraints beyond the schema's minimum steps.

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 it sets up a parameter sweep and runs simulations multiple times. The verb 'set up' and resource 'parameter sweep' are specific. However, it does not differentiate from sibling tools like cst_parameter_interpolation or cst_sensitivity_analysis, which perform related but distinct operations.

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 on when to use this tool versus alternatives, such as cst_parameter_interpolation or cst_sensitivity_analysis. There is no mention of prerequisites (e.g., parameter must exist, project must be open) or context for typical use cases.

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