set_node_property

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It discloses no side effects, no value-type coercion rules, no failure behavior, and no return value. For a mutating tool with zero annotation coverage this is a meaningful gap.

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?

A single front-loaded sentence that names the action immediately and then enumerates supported properties. Efficient, though the trailing ellipsis reads as an incomplete specification rather than a deliberate placeholder.

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?

With no annotations, no output schema, 0% schema coverage, four required parameters, and a large overlapping sibling set, the description is too thin. It fails to clarify the value format, the difference from set_node_input, or which node types/properties are supported, leaving an agent guessing on a non-trivial tool.

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 0%, so the description must compensate. It adds value by listing example property names and hinting that image takes a name/path (图片名或路径) and node_tree takes a group name. However, it says nothing about the polymorphic 'value' parameter, which accepts number/integer/boolean/string/array/null, so much of the semantics remains undocumented.

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 names a specific verb (设置/set) and resource (node property), and enumerates example properties (operation, blend_type, data_type, image, node_tree) that clarify the target. However, it doesn't distinguish this from the closely related sibling set_node_input, which also mutates node attributes, leaving some 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 on when to use this tool versus set_node_input, set_principled_inputs, set_gn_modifier_input, or set_color_ramp. The trailing ellipsis implies a broader scope but no conditions or exclusions are given, so an agent cannot reliably choose between the node-related siblings.

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