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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the auth context ('Requires HGRApi Header channel / ChannelOAuthId resolved internally'), but leaves the interaction between that internal resolution and the required channelOAuthId parameter vague, and says nothing about result scope or pagination (an output schema exists, which partly excuses this).

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?

Two short sentences, front-loaded with the operation and scope. The second sentence is terse and somewhat jargon-heavy ('HGRApi Header channel'), but no sentence is padding.

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?

A single-parameter read tool with full schema coverage, complete annotations, and an output schema does not need a long description. The description correctly covers purpose, scope, and auth context, which is all an agent needs to invoke it.

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% and the single parameter is already documented in-schema as coming from hgr_list_channels. The description adds only the 'one visible store' scoping and the internal resolving note, which does not meaningfully extend what the schema already says.

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?

Specific verb+resource: 'Reads Price Warrior dashboard/settings for one visible store', which is clearly a read operation against a named subsystem. It does not explicitly differentiate itself from the sibling hgr_update_price_warrior_settings, though the verb 'Reads' does most of the work.

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 scoping guidance is 'for one visible store', which is a constraint rather than a when-to-use rule. Nothing tells the agent when to call this versus hgr_update_price_warrior_settings or the numerous other dashboard/pricing tools, and no prerequisites or exclusions are stated.

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