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

No annotations exist, so the description carries the full behavioral burden and delivers none of it. It does not say whether the tool calls a model, mutates state, returns a prompt template or a ranked KOL list, or what 'edge-case handling' means operationally.

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 all of them are promotional filler ('in minutes', 'complete prompt, usage guide'). The text is brief without being front-loaded with anything an agent can act on.

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 one-optional-param tool with no output schema and no annotations, the description still leaves the core unknown: what a KOL match result looks like and what inputs beyond an optional query are expected. The marketing framing displaces the operational detail that is missing.

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?

Only one optional parameter exists and the schema documents it at 100% coverage, so the baseline is 3. The description adds no meaning about how 'query' scopes the analysis, but the schema already does that job adequately.

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 never states a concrete verb+resource. 'Turn expertise into output' and 'prompt pack helps restaurant and brand teams produce professional results' describe a product bundle, not an operation, and 'kols match' is never unpacked into what is actually matched with what.

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, when-not-to-use, or alternative is named. The sibling set contains directly comparable tools (fnb-influencer-match, sanhao-influencer-screening, fnb-ugc-campaign) yet the description gives no basis for choosing between them.

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