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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds some context that the channel/ChannelOAuthId is resolved internally and that this is a fixed endpoint rather than a generic caller, but its output statement ('returns the result or applies the effect') is a meaningless catch-all.

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?

The content is padded with template boilerplate ('Search terms:', 'not a generic endpoint caller', 'Requires HGRApi Header channel / ChannelOAuthId resolved internally') and repeats 'being watched operation' multiple times. It is not front-loaded with the distinguishing information an agent needs.

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?

With an output schema present, return values need not be explained, and the single fully-documented parameter is covered. What remains missing is a real explanation of how this dataset differs from the two adjacent analytics siblings, leaving the agent's selection decision under-informed.

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?

The single parameter is fully described in the schema (100% coverage), including its source from hgr_list_channels. The description mentions the channel input but adds no syntax or format details beyond the schema, so the 3 baseline applies.

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?

It states a specific verb and resource (GET the being-watched analytics for current-channel watcher analytics), which is better than a bare tautology. However, it never distinguishes this from the very similarly named siblings hgr_get_analytics_getwatchers and hgr_get_analytics_productsnotbeingwatched, leaving the actual semantic difference ambiguous.

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 guidance is circular: 'Use it when a client needs to run the being watched operation for current-channel watcher analytics' – it restates the purpose rather than giving when-to-use/when-not conditions. No mention of when to prefer getwatchers or productsnotbeingwatched.

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