Set Parameter Values

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

The description covers key behavioral aspects: atomic writes, undo wrapping, auto-coercion of vector values, and the return format with applied and error lists. However, it omits side effects like modifying the scene, permission requirements, or whether the operation is reversible (though undo is mentioned).

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 fairly concise, front-loading purpose and then detailing format and behavior. Every sentence adds value, though it could be slightly shorter without losing essential info.

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 no output schema, the description includes the return format. It covers input format, auto-coercion, and error handling. It does not mention document state requirements or handle validation, but the schema provides handle details.

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?

Description adds meaning beyond the schema by explaining that path can be an int id or DescID path with examples, and that list of 3 numbers auto-coerce to vectors. Schema coverage is 100%, so baseline is 3, but the added context raises it.

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 atomically writes parameter values with undo wrapping. It specifies the input format as an array of {path, value} objects and provides examples, making the verb and resource very specific. Among siblings like get_params and describe, this tool is distinctly for writing parameters.

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 for batch parameter writes with undo, but does not explicitly contrast with alternatives like get_params or set_keyframe. No guidance on when not to use it or prerequisites is provided, leaving some ambiguity.

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