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

With no annotations, the description carries the full disclosure burden. It hints that output is a "prompt pack with examples" rather than raw topic data, which is useful, but it never clarifies whether any external data is fetched, whether results are live trends or static templates, or what the response actually 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?

Two short sentences, but both are marketing filler ("production-ready", "structured, repeatable workflow you can run today") that do not help an agent decide or invoke. The one substantive fact, the prompt-pack deliverable, is buried at the end instead of front-loaded.

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 no annotations, no output schema, and dozens of near-duplicate topic/copy siblings, the description should clarify the input-to-output contract and differentiate itself. It does neither, leaving the agent unable to tell what calling it produces or when it beats an alternative.

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 schema has a single optional parameter with 100% description coverage, so the baseline is 3. The description adds nothing about how "query" scopes the analysis, but the schema already covers its meaning.

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?

"Viral topic miner system" essentially restates the tool name, and the rest of the text ("production-ready", "for marketing and operations leaders", "you can run today") is positioning copy rather than a verb+resource statement. The one concrete signal is that the deliverable is a "copy-paste prompt pack with examples", but it never says whether the tool mines topics, generates prompts about topic mining, or returns a workflow template.

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?

There is no guidance on when to use this versus the many adjacent siblings such as trending-topic-picker, viral-hook-writer, xhs-topic-kit, dy-topic-kit, or gzh-topic-kit. The audience mention ("marketing and operations leaders") hints at context but never states a triggering condition or an exclusion.

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