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

With no annotations, the description must explain behavior, but it only says the output "ships as a full prompt kit with step-by-step instructions" and mentions a support promise. It doesn't say whether this generates text, templates, or image guidance, whether the output is deterministic, or what happens with or without a query.

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 and front-loaded, which is good, but the first sentence misdirects ("restaurant & brand intelligence pack") and the last is pure sales copy ("30-day support promise") that takes space without helping the agent act.

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 generated-artifact tool with no annotations and no output schema, the description should at least say what the delivered kit contains and what it's used for. Instead it relies on marketing language, so an agent can't predict the output shape or confirm the tool is the right fit.

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 only one optional parameter, and its schema description ("Optional user query to scope the analysis") already covers it at 100% coverage, so the baseline is 3. The tool description adds nothing about how the query changes the generated kit.

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 says it will "generate a ready-to-use xhs photo kit workflow," which is close to restating the tool name, and it never explains what an "xhs photo kit" actually is or what the agent gets back. The opening line, "restaurant & brand intelligence pack," doesn't match the name and confuses the tool's purpose; it also doesn't distinguish this tool from siblings like xhs-cover-kit, xhs-template-kit, or dy/gzh/sph/zh-photo-kit.

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 choose this tool over the many xhs-* kit siblings, nor any preconditions or exclusion criteria. Phrases like "no prompt engineering needed" are marketing, not decision guidance.

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