cst_parameter_interpolation

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

With no annotations, the description must convey behavioral traits. It states the tool estimates performance via interpolation without running a simulation, which is helpful. However, it omits details like interpolation method, accuracy, or requirements (e.g., sweep data must exist).

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, efficient sentence that front-loads the core action and purpose. No unnecessary words or repetition.

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 explains the tool's purpose but does not specify what it returns (presumably interpolated results) or preconditions like a completed sweep. While the schema covers parameters, the lack of output schema detail and prerequisites limits completeness.

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 all three parameters (parameter, result_path, target_value). The description reinforces that interpolation is across sweep data points, adding context but not new parameter-level meaning. Baseline 3 is appropriate.

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 the tool's function: interpolating results from parameter sweep data to estimate performance at a specific parameter value, avoiding a new simulation. It distinguishes from sibling cst_parameter_sweep by emphasizing the interpolation over sweep execution.

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?

The description implies usage after a parameter sweep has been run, noting that no new simulation is needed. It provides clear context but lacks explicit when-not-to-use or alternative tools for related tasks.

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