cst_set_parameter

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

With no annotations, the description must fully disclose behavioral traits. It notes that values can be numeric or string expressions, but fails to mention side effects like triggering recomputation, requirement of an open project, or that setting a parameter may invalidate previous results.

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 extremely concise at two sentences, with no redundant information. The key action ('Set or create a design parameter') is front-loaded, and every word adds value.

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?

Given the tool's simplicity (3 parameters, no output schema) and the existence of sibling tools covering other parameter operations, the description covers the core functionality well. It could mention the optional 'description' parameter and whether the tool returns a result, but overall is sufficiently complete.

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?

The schema covers 100% of parameters with descriptions, establishing a baseline of 3. The description adds value by elaborating that 'value' can be a numeric or a string expression referencing other parameters, and provides concrete examples for 'name' (e.g., 'patch_length'). This enhances semantic clarity beyond the schema.

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 verb ('Set or create') and resource ('design parameter'). It distinguishes from sibling tools like cst_get_parameter, cst_delete_parameter, and cst_list_parameters, which perform different actions.

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 provides no guidance on when to use this tool versus alternatives (e.g., when to update vs create, or prerequisites like having an open project). No 'when not to use' or explicit context is given.

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