Set a node's radio parameters

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

Adds critical behavioral info beyond annotations: delayed effect after reboot and potential node disconnection if params don't match mesh. Annotations indicate idempotent and non-destructive, but description discloses side effects.

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?

Two concise sentences plus a warning. Front-loaded with main action. No extraneous words.

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 output schema present, no need to describe return values. Covers purpose, node targeting, and key behavioral warning. Schema fully documents parameters. Complete for the tool's complexity.

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 description adds little beyond listing parameter names. Baseline 3 as schema does the heavy lifting; description does not provide new semantic detail.

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?

Clearly states the action (set) and resource (radio parameters on a node). Specific about parameters (frequency, bandwidth, spreading factor, coding rate). Distinguishes from sibling tools like set_channel, set_node_name, etc., which deal with different aspects.

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?

Provides guidance on omitting `node` for home and warns about reboot and network drop-off. Does not explicitly mention when not to use or compare to alternatives, but the warning is valuable context.

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