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

With no annotations, the description carries the full burden but spends its words on sales copy ('no prompt engineering needed,' '30-day support promise'). It hints that the deliverable is a prompt kit with step-by-step instructions, but says nothing about permissions, cost, latency, whether the workflow is a template or executed, or how the query influences output.

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 at least two are marketing filler ('AI-powered ... intelligence pack,' '30-day support promise'). The actual capability is front-loaded behind promotional framing rather than the operative function.

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?

The tool is structurally simple (one optional param, no output schema), so the bar is modest, but the description still fails to state what the returned workflow contains, how the query scopes it, or how it differs from the numerous sibling campaign generators. An agent cannot confidently choose this tool over its neighbors.

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 100% schema description coverage, so the schema already explains its meaning. The description adds no param detail, but the baseline for fully documented single-param schemas is 4.

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 phrase 'generate a ready-to-use community viral event workflow' gives a verb and resource, but it is buried behind the marketing opener 'AI-powered restaurant & brand intelligence pack.' Nothing distinguishes it from the many campaign/event siblings such as viral-campaign-sop, ugc-campaign-builder, fnb-ugc-campaign, or restaurant-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 statement of when to use this tool, when not to, or which sibling handles adjacent cases. The agent is left to infer usage purely from the tool name, which is not enough given the crowded campaign/event toolset.

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