set_expression

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the language option and default but omits critical mutation behavior: whether an existing expression is overwritten, error conditions, permission requirements, or side effects. This is a significant gap for a write operation.

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 short and front-loaded with the main purpose. The args list is structured and each line is brief, though the parameter labels are somewhat redundant with the schema titles given the lack of schema descriptions.

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 mutation tool with four parameters, no annotations, and no output schema, the description is incomplete. It lacks usage context, prerequisites, error handling, and side-effect disclosure, leaving the agent unable to call it confidently in complex scenarios.

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%, so the description must compensate. It lists all four parameters with brief labels and provides allowed values and default for 'language' ('hscript' or 'python'), which adds some value. However, node_path, parm_name, and expression are only minimally described, leaving format expectations unclear.

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 states a specific verb and resource: 'Set an expression on a parameter.' This is clear and distinguishable from most siblings. However, it does not explicitly differentiate from related tools like get_expression or set_parameter, which limits it to a 4.

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?

There is no guidance on when to use this tool versus alternatives. The description only lists arguments and does not mention prerequisites, such as whether the node or parameter must already exist, or how it relates to get_expression or set_parameter.

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