Update node parameters

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

Describes strict atomic update: unknown parameter names fail entirely, bad values return partial success with error details. Annotations already indicate mutation (readOnlyHint=false) and non-destructiveness (destructiveHint=false), but description adds critical atomicity and error context.

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?

Three sentences: action, error behavior, usage alternatives. Front-loaded with primary purpose, no fluff. Perfectly sized for a mutation tool with moderate 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 2 required params, nested object, and no output schema, the description covers: what the tool does, error handling, parameter expectations, and complementary tools. No gaps for effective use.

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 provides 100% coverage for both 'path' and 'parameters'. Description adds value by showing parameter structure as key–value pairs with example 'period: 4, amplitude: 0.5' and linking to get_td_node_parameters for valid names.

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?

Description clearly states 'Modify an existing node by setting one or more of its parameters to constant values.' Verb 'modify' and resource 'node parameters' are explicit. Distinguishes from sibling 'animate_parameter' (dynamic values) and 'set_parameter_expression' (expression-based).

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?

Explicitly advises using 'get_td_node_parameters' for inspection and 'animate_parameter' for dynamic values. Provides clear when-to-use and when-not-to-use guidance with specific alternative tool names.

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