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. 'No setup, works in any LLM chatbot' is the only behavioral fact offered; nothing explains whether the tool returns a static prompt template, generates a plan, requires a model call, or how the playbook content is delivered back to the agent.

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?

Only three short sentences, but the lead sentence ('Save hours every week') is pure sales framing that carries no information an agent can act on. The substantive content is buried behind benefit language rather than front-loaded with what the tool does.

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 one optional parameter, the description is the sole source of behavioral information — yet it omits return format, output shape, and invocation semantics entirely. For a tool an agent must decide to call against dozens of near-identical UGC siblings, this is materially incomplete.

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 and the schema already documents it at 100% coverage, so the baseline of 3 applies. The description adds no meaning beyond the schema — it never explains how the query scopes the playbook or what happens when it is omitted.

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 is a 'restaurant ugc campaign toolkit' that provides 'a battle-tested prompt and operating playbook,' which gestures at the resource but never states a concrete action verb or what an invocation actually produces. It reads as marketing copy rather than a functional statement, and it does not distinguish itself from close siblings such as fnb-ugc-campaign, ugc-campaign-builder, or ugc-campaign-workbench.

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 trigger conditions, no prerequisites, and no mention of the many sibling tools that cover adjacent UGC/campaign territory. The only contextual hint is the domain ('restaurant/brand growth'), which an agent must infer usage from on its own.

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