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

No annotations are supplied, so the description carries the full burden, and it discloses almost no runtime behavior: nothing about what the tool returns, whether it is read-only or generates persistent artifacts, what 'ships as a full prompt kit' means for the response, or what happens with an empty query. The '30-day support promise' is commercial boilerplate, not behavioral information an agent can act on.

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 which the first ('AI-powered restaurant & brand intelligence pack') and third ('30-day support promise') are pure sales filler; only the middle clause conveys function. Front-loading is weak because the actual capability is buried after branding.

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 and no output schema, the description is the only source of truth about return values and side effects, and it leaves the agent guessing whether the tool returns a prompt kit, a generated campaign, or instructions. For a tool sitting in a dense cluster of overlapping UGC siblings, this is not complete enough to route reliably.

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 'query' parameter with full schema description coverage, so the schema already explains its meaning; per the baseline rule this lands at 3. The description does not clarify what the query scopes or what an omitted query produces, so it adds nothing beyond the schema.

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 contain a verb and resource ('generate a fnb ugc campaign workflow'), but the surrounding framing is marketing copy ('AI-powered restaurant & brand intelligence pack', 'prompt kit') that muddies whether the tool produces a campaign plan, a prompt template, or a workflow document. With siblings such as ugc-campaign-builder, ugc-campaign-workbench, and restaurant-ugc-campaign in the same namespace, the description offers no differentiation at all.

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 tool, when not to, or which sibling (ugc-campaign-builder, ugc-campaign-workbench, ugc-roi-model, restaurant-ugc-campaign) covers the adjacent need. The only usage-adjacent claim is 'no prompt engineering needed', which describes user effort rather than invocation conditions.

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