set_node_config

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

The description notes that the config 'takes effect the next time the node is (wiped and) started,' disclosing a non-immediate effect. Since no annotations are provided, this behavioral context is valuable. It does not mention whether the operation overwrites existing config or require permissions, but the timing detail is beyond what annotations would likely convey.

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 two concise sentences. The first front-loads the action and object; the second adds timing and a pointer to an alternative. Every sentence serves a purpose without redundancy.

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?

With an output schema present and only three simple parameters, the description covers the core purpose, timing, and alternative tool. It lacks elaboration on edge cases or permissions, but the provided information is sufficient for basic invocation given the sibling tool context and required parameters.

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 only refers to 'configuration text' without explaining lab_id, node_id, or the expected format/type of the configuration. The description does not add meaningful semantics beyond the schema's type strings.

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's function: 'Set a node's day-0 startup configuration text.' This is a specific verb and resource, and it distinguishes from the sibling tool extract_node_config by explicitly noting the alternative for capturing running config.

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?

The description provides explicit guidance: 'To capture a running node's current config instead, use extract_node_config.' It also clarifies when the setting takes effect ('next time the node is wiped and started'), telling the agent the timing of the operation.

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