Set channel

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is partly covered. The description adds the non-obvious behavior that passing 'none' stops the tuner, which is not in the annotations. It says nothing about effect on an active stream, auth/lockkey requirements, or failure behavior 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?

One short sentence with no filler, but the leading backticked endpoint fragment is cryptic and the actual verb ('set the tuner's channel') is buried in a code reference rather than front-loaded.

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 3-required-parameter mutation with no output schema and no annotation-level detail about side effects, the description should explain what happens to a currently-streaming tuner, what a successful call returns, and any lockkey requirement. None of that is present.

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, and it does partially: the endpoint path maps `tuner` to <n>, and the examples 'auto:651000000' / 'auto:60' show the modulation and freq_or_channel formats. However the parameter names themselves are never tied to the examples, and no constraints or valid modulation values are given.

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 gives the underlying endpoint (`/tuner<n>/channel`) and example values, which implies the tool sets a tuner's channel, but it never states the action in plain prose. It does not distinguish itself from siblings like hdhomerun_get_channel, hdhomerun_stop_tuner, or hdhomerun_set_channelmap.

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 usage signal is the trailing clause '`none` to stop', which explains one special value rather than when to pick this tool over stop_tuner or get_channel. There is no guidance on prerequisites such as lockkey or an in-progress stream.

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