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

The annotations already indicate an open-world, non-read-only operation, and the description adds the valuable detail that it also accumulates a local snapshot, implying a side effect beyond simply returning live data. This goes beyond what the annotations alone convey.

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 dense sentences: the first states the core behavior, and the second supplies routing guidance. There is no filler or repetition of schema information.

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 simple fetch-and-snapshot tool, the description plus schema covers invocation well: purpose, alternatives, parameters, and side effect are all present. It could mention what the returned hot-list entries look like, but the output is sufficiently implied by the tool's name and purpose.

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 input schema already provides full descriptions for all three parameters, so the baseline of 3 applies. The description itself does not add parameter-level detail, but since schema coverage is 100%, this is an acceptable gap.

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 clearly states the tool fetches current raw hot-topic rankings and accumulates local snapshots, using a specific verb and resource. It also explicitly differentiates itself from trend_intelligence and professional_intelligence, so an agent can select it correctly among siblings.

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 gives an explicit usage trigger: use when the user asks 'what's hot now'. It also names two alternative tools and the conditions that should route to each, making the when-to-use versus when-not-to-use decision unambiguous.

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