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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the mutation and blast-radius profile is largely carried by structured data. The description adds useful context about why the confirmation flags exist ('pricing rules can affect many listings') and that the channel header is resolved internally. It still doesn't say what the rule will start doing to prices, whether it can be undone, or what the response contains.

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?

Three short sentences, front-loaded with the action and scope, followed by the gating requirement. The final sentence is slightly compressed to the point of being hard to parse, but nothing is redundant.

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, non-idempotent, open-world write tool, the description covers the critical operational gate (both confirmation flags) and the channel resolution path. With an output schema present it needn't describe returns; the only real gap is the absence of any note on reversibility or on the update/delete alternatives.

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 100%, so the baseline is 3. The description corroborates that both confirmation booleans are required but adds no semantics beyond what the schema already says, and the closing phrase about 'HGRApi Header channel / ChannelOAuthId resolved internally' is ambiguous rather than clarifying the channelOAuthId parameter.

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 and resource ('Adds a pricing rule') plus scope ('for one visible store'), which is enough for an agent to know what happens. It does not name the sibling pair it sits between (hgr_update_pricing_rule / hgr_delete_pricing_rule), so differentiation is implied by the create/update/delete naming rather than stated.

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 gives real prerequisite guidance: confirmed=true and impactConfirmed=true are mandatory, and hgr_list_channels is the source of channelOAuthId. It never says when to add a new rule versus modifying an existing one with hgr_update_pricing_rule, so the alternative-selection guidance is only implied.

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