update_scad_parameter

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

The description mentions preserving comments and formatting and that it finds the named variable declaration. With no annotations, it partially describes behavior but lacks details on return value, side effects, or error handling, which are important for a mutation tool.

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 well-structured with a concise introductory summary followed by an Args list. Every sentence adds value, and the most important information is front-loaded. 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?

Given the tool has no output schema and no annotations, the description should cover return values and potential errors. It omits what the tool returns (e.g., modified code string) and does not mention validation or failure modes, leaving context incomplete.

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?

Despite 0% schema description coverage, the description includes an Args section that explains each parameter (scad_code, parameter_name, new_value) beyond their types and titles, providing clear meaning and usage context.

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 'Update a parameter value in OpenSCAD code', identifying a specific verb and resource. It distinguishes from siblings like 'modify_scad_module' by focusing on parameter value replacement, but does not explicitly differentiate from other parameter-related tools.

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 says 'Use this to tweak dimensions without regenerating the entire model', implying when to use it. However, it does not specify when not to use or provide alternatives, such as when a full regeneration is needed.

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