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

No annotations exist, so the description carries the full burden. The one useful signal is that the response bundles a prompt, a usage guide, and edge-case handling, implying a static template-style payload rather than computed analysis. However, it never states what the agent actually receives, whether the optional query changes the output, or any constraints on use.

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 where the first ('Turn expertise into output') is empty and the second is claim-based marketing. Only the final sentence about included contents carries information, and it is placed last rather than front-loaded.

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 a single optional parameter, the description is the only source of behavioral and output information, and it does not say what a 'prompt pack' return looks like or what task the agent should pair it with. Given the dense sibling space of live-selling and script tools, this leaves the agent materially under-informed.

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 its meaning. The description adds nothing about how the query scopes or alters the returned prompt pack, but with full schema coverage the baseline of 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 leans on marketing phrasing ('Turn expertise into output', 'produce professional results in minutes') and essentially restates the tool name as a 'live selling script prompt pack.' It never states a concrete verb+resource outcome, such as whether it generates a script, returns a reusable prompt template, or produces a full usage guide, so an agent cannot distinguish it from the many live/script siblings.

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 prerequisites, and no mention of alternatives in a sibling list that contains live-room-script, live-script, live-talk-script, dy-live-kit, and sph-live-kit. The only audience hint ('restaurant and brand teams') is a targeting statement, not a selection rule.

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