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

Beyond the readOnly/openWorld annotations, it discloses a non-obvious data semantics: trending_count counts all flagged reels with no recency filter, while trends_search on global/for_you cuts at 7 days, and on tab=my_authors the relation inverts. It also warns against quoting the counter to users. That is exactly the kind of behavioral context annotations cannot carry.

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?

Purpose is front-loaded in the first sentence, followed by the counter caveat in a clearly marked block. The caveat is long but earns its place by preventing a user-facing misstatement; the two paragraphs of tab-by-tab comparison could be tightened slightly.

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 zero-required-parameter read-only listing with no output schema, the description covers what the tree contains, which parameter values it supplies downstream, and how its counter relates to other tools. Nothing an agent needs in order to call it and interpret the result is missing.

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%, so both `group` and `with_keywords` are already documented in the schema. The description never mentions either parameter, so with the schema doing all the work the baseline of 3 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?

The description names the resource precisely (a topic tree of groups and niches with RU/EN names, keywords and a trending count) and implicitly separates it from trends_search by explaining that this is the source of the `niche` values. An agent can tell what it returns without opening the schema.

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?

It states the canonical use case clearly: fetch valid niche slugs and group keys before calling trends_search, and that both forms are accepted there. It does not contrast with sibling niche_search or say when this listing is unnecessary, so it falls short of a full 5.

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