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

No annotations are supplied, so the description carries the full disclosure burden and largely fails it — no indication of whether the call is read-only, what the optional query scoping changes, latency, or cost. The closest thing to behavioral content is that it 'ships as a full prompt kit with step-by-step instructions,' which hints at an artifact-style return but is framed as product marketing rather than tool 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 short sentences, but a large share of the text is promotional filler — 'Instantly,' 'no prompt engineering needed,' '30-day support promise' — that consumes space without informing invocation. The one useful signal (that a workflow artifact is produced) is buried after the vague 'intelligence pack' framing.

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 output schema and only one optional parameter, the description is the sole place an agent could learn what comes back, yet it never says whether the result is a prompt kit, a step-by-step plan, or an analysis. For a generate-style tool this is a material omission, and the sibling-overlap ambiguity is left unresolved.

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% for the single optional 'query' parameter, so the schema already explains scoping; per the baseline rule this lands at 3. The description adds nothing about how the query influences the generated workflow, but no compensation is strictly required.

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 says it will 'generate a ready-to-use ugc campaign workbench workflow,' which essentially restates the tool name back at the reader rather than defining an operation. 'AI-powered restaurant & brand intelligence pack' broadens rather than sharpens scope, and nothing distinguishes it from close siblings such as ugc-campaign-builder, restaurant-ugc-campaign, fnb-ugc-campaign, or ugc-roi-model.

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, when-not-to-use, or alternative-naming guidance anywhere in the text. 'No prompt engineering needed' and '30-day support promise' are sales claims, not selection criteria, so an agent facing a crowded sibling list has nothing to route on.

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