node_exec

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

With no annotations, the description carries the full behavioral burden and it does add real context: Base64 transport and secret scrubbing of output. It omits other traits an agent needs for arbitrary code execution — the destructive-command gate, sudo password requirements, timeout kill behavior, and output format — so the disclosure is partial rather than complete.

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 with zero filler; the verb leads and the constraints follow. Nothing can be trimmed without losing information.

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?

This is an eight-parameter arbitrary code execution tool with no annotations and no output schema, so the description must explain return values, failure/timeout semantics, and the destructive-confirmation gate — it explains none of these. For a tool of this risk level the single sentence is materially under-specified.

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 100%, so the baseline is 3 and the eight parameters are already documented individually. The description's mention of Base64 transport and secret scrubbing weakly reinforces the 'script' and 'secret_env' parameters but adds no syntax, format, or precedence detail beyond the 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 names a specific verb and resource ('Execute a shell/PowerShell script') and constrains the targets to '@appliance', '@bastion', or a configured TargetNode, which separates it from file-oriented siblings like node_read_file and node_patch_file. It does not explicitly name a sibling it is not, so sibling differentiation is left partly to inference.

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?

It says where the script runs but never says when to choose node_exec over node_patch_file, node_transfer, or node_db_query, nor when it is inappropriate. The only guidance in the whole definition sits in the schema ('confirm_destructive'), not in the description.

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