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

No annotations are supplied, so the description carries the full burden and largely fails. The only behavioral hint is "delivered as a copy-paste prompt pack with examples," which vaguely suggests the return is a prompt artifact rather than finished copy, but it never states this clearly, nor whether cost, auth, or limits apply.

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 (two sentences) but invests both in marketing framing — "production-ready," "run today," "marketing and operations leaders" — rather than in front-loading the actual operation. Trimmed of sales language, almost nothing remains.

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 and no output schema, the description should explain what the tool returns and how it differs from siblings. It does neither, so an agent cannot confidently decide to call it or predict the result shape.

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 a single optional parameter (query) at 100% schema coverage, so the schema already explains its meaning. The description adds nothing about how the query scopes the output, leaving the baseline 3 appropriate.

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?

"xhs adcopy kit" implies Xiaohongshu advertising copy generation, giving a rough verb+resource pairing. But the description never states plainly that it writes ad copy, and it does nothing to separate it from the many sibling kits (dy-adcopy-kit, gzh-adcopy-kit, sph-adcopy-kit, xhs-viral-copywriter). An agent can guess the domain but not the precise operation.

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?

No when-to-use guidance at all. There is no mention of which tasks belong here versus xhs-viral-copywriter, xhs-title, xhs-hook-master, or the parallel dy/gzh/sph/zh adcopy kits, so routing among the ~500 siblings is left entirely to guesswork.

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