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

No annotations are provided, so the description must carry the full behavioral burden, and it discloses nothing: no output format, no side effects, no prerequisites, no limits. "Ships as a full prompt kit" and the "30-day support promise" describe a product purchase, not 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?

It is short, but every sentence is promotional filler ("instantly", "no prompt engineering needed", "30-day support promise") and none is front-loaded with a functional statement of what the tool does. Conciseness is achieved by omission rather than by editing.

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 generator tool with no output schema and no annotations, the description should explain what artifact is returned and how the query influences it. Instead an agent finishes reading with no idea what calling this tool would produce.

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?

The single optional `query` parameter is fully documented in the schema, so the schema carries parameter meaning on its own. The description adds no additional semantics about how the query scopes the generated workflow, so the baseline 3 applies.

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 ("generate a ready-to-use script gen tool workflow") without saying what the tool actually produces, and it opens with an unrelated claim about a "restaurant & brand intelligence pack" that muddies rather than clarifies scope. It does not distinguish this tool from near-identical siblings such as qt-script-helper-tool or qt-case-gen-tool.

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 guidance on when to use this tool, when not to, or which of the many sibling tools to pick instead. Phrases like "no prompt engineering needed" are marketing, not selection criteria.

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