set_power

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

With no annotations provided, the description carries the full burden. It discloses the core effect (power on/off) and an implementation behavior (switch_dp override/default behavior), which goes beyond the bare schema. However, it does not mention permissions, reversibility, edge cases, or failure behavior.

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 compact and front-loads the main action in the first sentence. The second paragraph adds necessary parameter nuance without waste. Every sentence earns its place.

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 three-parameter tool with an output schema, the description covers the core purpose and the one non-obvious parameter. It could briefly mention that 'device' refers to a device identifier from list_devices, but the tool name and sibling context make that inferable.

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 explains switch_dp's override function and the recommended 'unset' default for most devices, but does not clarify the 'device' parameter beyond its name and type. 'on' is self-explanatory but still undocumented in the schema.

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 an explicit action ('Turn a device on or off') on a clear resource (a device). This is distinct from sibling tools like set_brightness or set_color, which target different aspects of device control.

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 implies when to use the tool by defining its function, but it does not explicitly contrast with alternatives such as set_datapoint, nor does it state when not to use it. The switch_dp guidance is parameter-level, not tool-selection-level.

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