Set parameter expression / bind / constant

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

Adds rich behavioral context beyond annotations: explains fail-forward batch behavior (per-item failures become warnings), partial batch returns useful results, reset restores defaults, unbind freezes current value and drops the driver, and the exec path requirement. This significantly exceeds what annotations provide.

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?

Four sentences, each carrying essential information: purpose, modes, batch behavior, and usage guidance. No fluff or repetition; structure is logical (purpose -> modes -> behavior -> alternative).

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 tool with no output schema, the description covers the key operational aspects: all five modes, batch semantics, prerequisites, and the relationship to a sibling tool. It gives the agent enough to invoke correctly and anticipate results.

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%, so baseline is 3. The description restates mode behavior that is already in the schema (expression/bind/constant/reset/unbind), but adds the fail-forward and environment variable context, which is more about tool behavior than parameter semantics. Minimal additional parameter-specific value beyond schema.

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 opens with a specific verb and resource: 'Set one or more parameters on a node to an expression, bind expression, or constant value.' It clearly distinguishes from siblings by mentioning it avoids the raw-Python escape hatch and explicitly references execute_python_script as an alternative.

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 states when to use this tool instead of execute_python_script when TDMCP_RAW_PYTHON is off. It also provides a critical prerequisite for reset/unbind modes (TDMCP_BRIDGE_ALLOW_EXEC=1), giving clear usage conditions.

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