Update device value

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds no behavioral context such as side effects, permission requirements, or caution about overwriting device values. 'Manual update' provides no meaningful disclosure beyond the structured annotations.

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 short but under-specified rather than helpfully concise. 'Manual update' is filler that does not earn its place, and the two fragments provide no meaningful structure or front-loaded actionable 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?

Given the tool's destructive annotation and large sibling set, the description is incomplete: it fails to explain when to invoke it, what behavior to expect, or how nvalue/svalue updates interact with the target device. The schema and annotations carry nearly all the useful context.

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 100%, so parameters are already fully documented. The description's 'Preferred: idx' merely duplicates what the idx parameter description already states ('preferred over name when known'), adding no new semantic value.

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 'Manual update' is essentially a tautology that restates the title without specifying what device value is being updated or how. It does not distinguish this tool from siblings like set_switch_state, rename_device, or call_domoticz_api.

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 only guidance, 'Preferred: idx', addresses parameter choice rather than when to use this tool. There is no mention of when to choose update_device_value over alternative sibling tools or what conditions make it the right choice.

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