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

No annotations are supplied, so the description bears the full burden. "No setup, works in any LLM chatbot" hints that the output is a self-contained prompt, but it says nothing about output format, length, whether the tool performs any analysis, or side effects — a substantial gap for a tool with zero annotation coverage.

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?

Only two sentences, but both are sales copy ("Save hours every week", "battle-tested", "No setup") rather than front-loaded functional information. Nothing is wasted in length, yet the space is spent on claims instead of purpose.

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 output schema and no annotations, the description should explain what the kit produces and how to apply it. Instead it stops at a value proposition, leaving return shape, scope, and the role of 'query' entirely undefined.

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?

Schema description coverage is 100% for the single optional 'query' parameter, so the baseline of 3 applies. The description adds no meaning beyond the schema about how a query scopes the result, leaving the parameter's effect unclarified.

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 mostly restates the name ("This xhs live kit toolkit") plus a marketing claim about a "prompt and operating playbook for restaurant/brand growth." It never states a concrete action or deliverable, so an agent cannot tell what calling it actually returns — a prompt template, a strategy doc, or advice.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. With dozens of near-identical siblings (dy-live-kit, gzh-live-kit, sph-live-kit, zh-live-kit, and the other xhs-*-kit tools), the description offers nothing to route an agent between them.

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