Set parameter expression / bind / constant

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

Annotations indicate non-read-only and non-destructive. The description adds that multiple assignments are applied fail-forward, with per-item warnings, which is valuable beyond annotations. No contradictions.

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?

Description is 3 sentences, front-loaded with purpose, and every sentence adds essential information (purpose, modes, fail-forward, usage alternative). No waste.

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's complexity (three modes, batch processing), the description covers all necessary aspects: purpose, modes, failure behavior, and alternative tool. Schema and annotations are comprehensive, so description is complete.

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 100% with detailed descriptions for path and assignments, including enum for mode. The description adds no new parameter-specific details beyond what's in the schema, but confirms the three modes. Baseline 3 is appropriate.

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 the tool sets parameters on a node to expression, bind, or constant, avoiding raw Python. It distinguishes from siblings like 'execute_python_script' and 'set_parameters_batch' by specifying the three modes and the fail-forward behavior.

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 mentions using this tool instead of 'execute_python_script' when raw Python is off, providing clear guidance on when to use. Also describes fail-forward behavior for batch assignments.

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