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

With no annotations, the description carries the full burden. It hints at the output artifact ("ships as a full prompt kit with step-by-step instructions"), which is mildly useful, but says nothing about whether the tool performs analysis or only returns a template, what the response looks like, or any cost/latency/side-effect profile. Most of the text is promotional rather than behavioral.

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?

Three short sentences, but the second half is filler for an agent's decision-making ("no prompt engineering needed", "30-day support promise"). The actual capability statement is present up front, but a meaningful share of the text does not earn its place.

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-parameter tool with no output schema, the description should at least clarify what is returned and how it relates to the many influencer/KOL matching siblings. It leaves both unanswered, so an agent cannot confidently route to this tool in a 500+ tool catalog.

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 with 100% schema description coverage ("Optional user query to scope the analysis"), so the schema already documents it fully. The description adds no further meaning about how the query scopes the generated workflow, 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?

The description does name a resource and action ("generate a ready-to-use sanhao influencer screening workflow"), so the agent can infer this produces an influencer-screening kit rather than performing screening itself. However, the opening line ("AI-powered restaurant & brand intelligence pack") is marketing framing that blurs the purpose, and nothing distinguishes it from close siblings like fnb-influencer-match or kols-match-tool.

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 statement of when to use this versus the many sibling screening/matching tools, no prerequisites, and no exclusions. The only guidance is a sales claim ("no prompt engineering needed") and a support promise, neither of which helps an agent choose this tool.

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