set_power

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

Annotations already declare this is not read-only, is open-world, and has a destructive hint. The description adds useful behavioral context: target temperature is preserved, a connected Dock Pro is required, and standby is not a mains disconnect. That clarification is valuable beyond the annotations, though error behavior is not described.

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 three tight sentences with the main action front-loaded, followed by the precondition and an important behavioral caveat. Every sentence contributes useful 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?

For a simple two-parameter tool with no output schema, the description covers the action, parameter meaning, prerequisite, and a key caveat about standby. The main remaining gap is lack of detail about how target should be identified.

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 carry parameter meaning. It clearly defines the on parameter as active (true) or thermal standby (false) and indicates target is a confirmed target. However, it does not specify the target format or accepted values beyond that.

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 states a specific verb and resource: setting one confirmed target to active or thermal standby. It also distinguishes the action from sibling set_temperature by noting that target temperature is preserved. An agent can understand the operation without opening the schema.

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 gives clear usage context: use this to switch a confirmed target between active and standby, and it requires a connected Dock Pro. It does not explicitly name alternatives or when not to use it, but the preserving-temperature note helps differentiate it from temperature-setting tools.

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