Set port power

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

Annotations already mark the operation as non-read-only, idempotent, and non-destructive. The description adds useful behavioral nuance by stating that the power setting applies to every mode and clarifying the On-mode meaning of on_power, plus the partial-update semantics.

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 compact sentences front-load the core action and range, then give the mode-scope and partial-update guidance. No filler or repetition of schema details.

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?

The description plus fully documented schema, annotations, and output schema give an agent enough to call the tool safely and correctly. The only notable caveat, user_authorized must be true, is already explicit in the schema.

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?

All five parameters are fully described in the schema with ranges, defaults, and constraints, so the description need not repeat them. It adds only the partial-update convention, which is a useful extra but not a substitute for schema coverage.

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?

States a specific action (set) on a specific resource (port power levels) and clarifies the 0-10 range and both on/off states. This differentiates it from sibling tools focused on mode, timer, cycle, schedule, and triggers.

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?

Gives actionable guidance about partial updates ('Pass only the values you want to change') and clarifies that the setting applies to every mode, with On-mode behavior spelled out. It doesn't explicitly name sibling alternatives or exclusion conditions, but the context is sufficient to select this tool over the read/set siblings.

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