Set a node's transmit power

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

Discloses important behaviors beyond annotations: the PA stage can amplify the configured dBm, implying the actual output may differ. Annotations already indicate idempotency, so no contradiction. Adds context about destructive potential (legal issues) despite destructiveHint=false.

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 sentences plus a warning emoji. Every word adds value. Front-loaded with action, then parameter details, then critical caution. Excellent conciseness.

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?

Covers purpose, parameters, default behavior, and a critical safety warning. Output schema exists and need not be described. Very complete for a simple setting tool.

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 covers all params fully (100%). Description adds value by clarifying the default for 'node' and giving an admin command equivalent, which helps understanding. No ambiguity remains.

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 action (set radio transmit power) and resource (node). Specifies unit (dBm), distinguishes from siblings like set_radio by focusing on power only. Includes equivalent admin command for context.

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 default target (home node when omitted) and warns about legal/regional limits and PA stage. Could be improved by contrasting with set_radio's broader scope, but the guidance is clear and actionable.

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