homey_set_capability

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

No annotations are provided, so the description carries the full burden. It only says 'set' without disclosing side effects, whether the operation is reversible, permission requirements, or possible failure modes (e.g., offline device). This is insufficient for a mutation tool.

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 a single sentence with no wasted words. It front-loads the core action ('Set a capability value on a device') and provides illustrative examples without redundancy.

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 3-parameter setter with no output schema, the description is adequate but has gaps: it lacks usage guidance and behavioral transparency. The schema covers parameter meaning, so the tool is minimally viable, but not richly contextualized.

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?

The schema description covers all 3 parameters at 100%, so the baseline is 3. The description adds slight value by associating example values with capability types (e.g., on/off implies boolean, dim implies number), but this largely overlaps with schema examples.

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 clearly states the action: 'Set a capability value on a device' with concrete examples like 'turn on/off, dim, target_temperature'. This is a specific verb+resource that distinguishes it from the sibling read/list tools.

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 usage via examples (controlling device state), but does not explicitly state when to use it versus alternatives like homey_list_devices or homey_get_sensor_readings. No exclusions or alternatives are provided, making it merely implied context.

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