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

No annotations exist, so the description carries the full burden and does little: it hints the output is "a full prompt kit with step-by-step instructions" but never states whether the tool is read-only or generating, whether it has side effects, or what the response contains. The 30-day support promise is commercial boilerplate irrelevant to invoking the tool.

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 marketing claims rather than operational information; "no prompt engineering needed" and "30-day support promise" consume space without helping an agent decide or call. The front-loaded phrase is the misleading "restaurant & brand intelligence pack" rather than the actual function.

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 simple one-optional-param tool with no output schema, the description should define the deliverable and platform. Instead it leaves the agent unable to tell this apart from a dozen sibling quote kits and introduces a wrong domain framing (restaurant/brand intelligence).

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 whose schema description is present (100% coverage: "Optional user query to scope the analysis"), so the schema already does the work. The tool description adds no meaning about how the query scopes output, so the baseline 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?

"AI-powered restaurant & brand intelligence pack" is actively misleading for a tool named gzh-quote-kit, where gzh denotes WeChat Official Account and the sibling family (dy-quote-kit, sph-quote-kit, xhs-quote-kit, zh-quote-kit) makes clear this is a platform-specific quote-content kit. The second sentence only restates the tool name ("generate a ready-to-use gzh quote kit workflow") without saying what content it actually produces or which platform it targets.

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 prerequisite, and no mention of the many near-identical siblings (dy-, sph-, xhs-, zh-quote-kit) that an agent must choose between. The only conditional-sounding text ("no prompt engineering needed", "30-day support promise") is sales copy, not selection criteria.

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