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

With no annotations, the description carries the full behavioral burden, and it mostly delivers promotional claims ('AI-powered', '30-day support promise'). The only concrete behavioral hint is that it produces a 'full prompt kit with step-by-step instructions', with no information on output format, length, or limits.

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 sales copy, including a '30-day support promise' that is irrelevant to invocation. The actual functional content is compressed into a single clause, and the front-loaded emphasis is on branding rather than capability.

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 one-parameter tool with no output schema and no annotations, the description should say what comes back and in what form. Instead it leaves the return value as an implied 'prompt kit', which is too vague for an agent to act on confidently.

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% and there is only one optional 'query' parameter, so the schema already documents it. The description adds nothing about how the query scopes the analysis, keeping this at the baseline.

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 will 'generate a ready-to-use live script workflow' for 'restaurant & brand intelligence', but the phrasing is marketing copy rather than a specific verb+resource statement. It does not distinguish the tool from the many sibling live-script tools such as live-room-script, live-selling-script, live-talk-script, dy-live-kit, or chain-fnb-script-master.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. 'No prompt engineering needed' is a selling point, not a selection criterion, so an agent has no basis for choosing this over its many live-script siblings.

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