set_parameter

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

With no annotations, the description carries full burden for behavioral disclosure. It only states what the tool does, but does not mention side effects (e.g., overwriting existing values), error conditions, required permissions, or return behavior. This leaves significant gaps about what happens when the tool is invoked.

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 sentence with no filler or redundant text. Every word contributes to the core meaning, making it concise and well-structured.

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 simple setter tool, the description is minimal but misses key contextual details such as how 'value' is interpreted (int, string, expression), whether setting a parameter may trigger a cook, and how node_path is specified. Given there is no output schema or additional documentation, the description is insufficient for an agent to use it correctly in edge cases.

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 description coverage is 0%, and the description does not explain any of the three parameters (value, node_path, parm_name). Even though the parameter names are somewhat self-explanatory, the description adds no semantic meaning about value types, formats, or relationships between parameters.

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 uses a specific verb ('Set') and resource ('parameter value on a node'), and the word 'single' distinguishes it from sibling tool 'set_parameters' which handles multiple parameters at once. This clearly states what the tool does without ambiguity.

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 is provided on when to use this tool versus alternatives like set_parameters, set_expression, or set_keyframe. The description gives no context for tool selection, prerequisites, or situations where this should be preferred.

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