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

No annotations are provided, so the description carries the full burden. It mentions that the pack includes a prompt, usage guide, and edge-case handling, but says nothing about what invoking the tool returns, whether it generates fresh topics or serves a static template, or any constraints or permissions.

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?

It is short, but the opening sentences are marketing filler ('Turn expertise into output', 'in minutes') that do not front-load the actual capability. The useful detail about included materials comes last, and overall information density is low.

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 prompt-pack tool with a single optional parameter, an agent needs to know the target platform, the kind of topic output, and how it differs from the many sibling kits. None of that is present, so the definition is not complete enough to select and invoke confidently.

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?

There is one optional parameter ('query') and the schema description coverage is 100%, so the schema already defines it. The description adds no meaning about how the query scopes analysis, so 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 relies on marketing phrasing like 'Turn expertise into output' and 'topic kit prompt pack' rather than a specific verb and resource. It never states what a 'zh-topic-kit' actually produces (e.g., Zhihu topic ideas, titles, or a reusable prompt template), and with dozens of sibling '-topic-kit' tools it does nothing to differentiate itself.

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 indication of when to use this tool instead of alternatives such as zh-topic-kit's peers (xhs-topic-kit, gzh-topic-kit, dy-topic-kit, viral-topic-miner, trending-topic-picker). The only audience hint is 'restaurant and brand teams,' which is not a usage condition.

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