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

No annotations exist, so the description carries the full burden, and it fails to explain what the output is, whether it diagnoses, rewrites, or grades a script, or what a '30-day support promise' means operationally. The claims are promotional rather than behavioral.

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?

Most of the text is sales copy: 'AI-powered', 'instantly', 'no prompt engineering needed', and a 30-day support promise that carries no invocation value. The useful content, if any, is buried behind marketing framing.

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 vague name, the description should clarify the actual transformation it performs on a script. Instead it describes packaging and support terms, leaving the core behavior undefined.

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 has 100% schema coverage, so the schema already documents it; the description adds nothing about how scoping works. Baseline 3 applies when coverage is high and the description neither helps nor misleads.

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 and wraps it in marketing language ('shortvideo script doctor workflow') without stating what the tool actually does to a script. It calls itself a 'prompt kit' rather than describing the operation, and it never distinguishes itself from the many sibling script tools such as douyin-script-doctor or short-drama-script-generator.

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 prompt engineering needed' implies usage is trivially easy, but there is no statement of when to pick this over the sibling script tools or the douyin-script-doctor variant. An agent gets no routing signal.

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