Set item

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the cryptic '(implicit get-back)' clause; it says nothing about the lockkey authorization requirement, whether invalid item names error or are silently dropped, or which items are destructive.

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?

It is short and front-loaded, but the single backticked sentence packs the entire meaning into CLI syntax plus a parenthetical that is more cryptic than concise; a sentence of plain-language intent would cost little and add much.

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 an open-world mutation tool with zero schema documentation, no output schema, and a required auth-like parameter, the description is far too thin. It should enumerate or reference valid item names and explain lockkey and error behavior.

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 coverage is 0% for three parameters. The CLI snippet loosely maps `<item>` and `<value>` to the name/value params, but `lockkey` — likely a required auth token for protected settings — is entirely unexplained in both schema and description.

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 identifies a generic setter for an arbitrary `<item>` via the underlying CLI syntax, and `(implicit get-back)` hints that the value is read back. But it never says what items are settable or what domain this applies to (HDHomeRun device config), leaving the purpose vague relative to the many typed setters like hdhomerun_set_channel.

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?

There is no statement of when to use this generic setter versus the dozens of typed siblings (hdhomerun_set_channel, hdhomerun_set_lockkey, hdhomerun_set_target). An agent must infer that this is a fallback for items without a dedicated tool.

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