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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about what the tool returns, whether it mutates state, what the "prompt kit" consists of, or how the workflow is delivered. Sentences about a support promise occupy space that should describe observable behavior.

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 sentences of promotional copy with no operational content; the closing "30-day support promise" is pure sales padding that does not help an agent decide or invoke. Front-loading is wasted on a category claim rather than a capability statement.

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 annotations, no output schema, and a single loosely described parameter, the description needed to explain what gets produced and in what form. Instead it describes packaging and support terms, so an agent still cannot predict the result of a call beyond the name.

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% and there is a single optional `query` param, so the schema already defines its meaning. The description adds nothing about how `query` scopes the analysis, so it neither helps nor misleads — 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 restates the tool name ("fnb influencer match") inside marketing framing ("AI-powered restaurant & brand intelligence pack", "Instantly generate a ready-to-use ... workflow") without specifying what the tool actually does when invoked. It never distinguishes itself from plausible siblings such as sanhao-influencer-screening, kols-match-tool, or fnb-ugc-campaign.

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 named alternative. The only hints ("no prompt engineering needed", "30-day support promise") are purchase assurances, not invocation guidance, leaving the agent to infer context from the name alone.

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