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 behavioral: no output format, length, structure of the 'storyboard', whether it is a single-shot or multi-scene deliverable, or what happens when no query is given. The only real signal is the promised artifact ('ready-to-shoot storyboards'), which is a hint at output shape but not a specification.

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 a single sentence with no padding, but it spends its words on unglossed jargon (PREP, contrast, FIRE, RIDE, IP-reinforcement) that an agent cannot act on. Front-loading the persona credential over the actual capability is the wrong ordering for tool selection.

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 crowded family of overlapping script-writing siblings, the description should clarify scope, deliverable, and differentiation. It supplies none of these, leaving an agent unable to predict what it will get back or why it should choose this tool over a dozen alternatives.

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 it. The description adds nothing about how the query scopes the brief or what a well-formed query should contain, which is the baseline expectation when the schema does the documenting.

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 conveys that this produces short-video shot scripts/storyboards and names the target platforms, so the general resource is identifiable. However, the framing is a persona ('20-year streaming-video scriptwriter') rather than a verb, and it never states plainly what the tool does — generate a script, rewrite one, or storyboard an existing idea. With near-identical siblings like short-video-script, short-video-script-pro, short-video-script-doctor and shoot-script-studio, that ambiguity matters.

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 sibling to pick instead. The list of platforms implies suitability for cross-platform short video but does not say the user should choose this over short-video-script-pro or the platform-specific dy-/xhs-/sph-script kits. Nothing about prerequisites or input expectations either.

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