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

Annotations already declare destructiveHint=true and non-idempotent, and the description adds value on top: it explains why the confirmation gates exist ("source settings can affect many listings") and discloses internal resolution of the HGRApi Header channel / ChannelOAuthId. It does not describe failure behavior or what exactly is overwritten on save, so it stops short of 5.

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?

Four short sentences ordered from purpose to scope to safety gate to auth, with no filler and the key negative constraint placed early. The final sentence about internally resolved HGRApi Header channel partially duplicates the channelOAuthId parameter and reads slightly ambiguously.

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 destructive mutation with an output schema and mostly documented parameters, the description covers the essentials: single-setting scope, blast-radius rationale, mandatory confirmation gates, and the fact that channel context is resolved internally. Only error/partial-failure behavior is unaddressed, which is a minor gap given the output schema exists.

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 75% and the schema itself richly documents Key, Value serialization and SourceId, so the description does not need to repeat them. The description only reinforces that exactly one setting is saved and gives a rationale for the confirmed/impactConfirmed flags, which the schema parameters already state; net added meaning is minimal.

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?

States a specific verb (saves) and resource (one exact setting in HGRWeb Supplier configuration), and adds a negative scope clause ruling out supplier enable/disable/suspend/re-enable, which distinguishes it from status-changing siblings. It does not explicitly contrast with the closest sibling hgr_save_channel_setting, so sibling differentiation is only partial.

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 makes clear this is for a single setting at a time and states that confirmed=true and impactConfirmed=true are prerequisites tied to user confirmation of high-impact consequences. It never explicitly routes the agent between this tool and alternatives (e.g. channel-level vs source-level settings), leaving that to be inferred from the resource name.

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