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 nothing operational. It mentions the payload contents ('the complete prompt, usage guide, and edge-case handling'), which implies the tool returns prompt material rather than executed output, but it never says whether anything is persisted, whether the optional query is required for meaningful results, or what a caller receives back.

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?

It is short, but three sentences of promotional language earn little: 'Turn expertise into output' is a meaningless opener that occupies the front-loaded position where the actual capability should be. The remaining sentences describe packaging rather than behavior, so brevity comes from omission, not discipline.

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?

For a tool with no annotations, no output schema, and a deliberately vague single optional parameter, the description should explain what the model actually produces and how a caller should frame the query. Instead it leaves the core question of input and returned artifact unresolved, which is inadequate even for a simple generator.

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?

With a single optional parameter at 100% schema description coverage, the schema already defines 'query' as an optional scoping input, so the baseline of 3 applies and the description neither adds nor contradicts anything. It edges slightly above baseline only because the 'restaurant and brand teams' framing lets an agent infer what kind of query is appropriate.

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 ('This campaign idea generator prompt pack') and wraps it in marketing copy ('Turn expertise into output', 'produce professional results in minutes') rather than stating a concrete verb and resource. It never clarifies whether the tool generates campaign ideas, returns a reusable prompt template, or packages a guide, and it draws no distinction from the many campaign siblings (mkt-campaign-library, store-campaign-planner, ugc-campaign-builder, viral-campaign-sop).

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?

The only contextual signal is a target audience ('restaurant and brand teams'), which is a hint at scope but not a when-to-use rule. There is no statement of when this should be chosen over alternatives, no exclusions, and no prerequisites, despite dozens of overlapping campaign and copywriting tools in the sibling list.

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