create_drama

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

With no annotations, the description carries the full burden. It discloses that the tool creates a shell, auto-creates empty episodes, returns IDs, is free, and that minimal input leads to downstream inconsistency and rework. It doesn't mention idempotency or permissions, but the core side effects are transparent.

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 compact sentences front-load the main action, then add a prioritized setup warning and the return-value summary. The structure is efficient and every sentence carries meaningful guidance, with only minor repetition of '免费'.

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 41-parameter tool with no output schema, the description adequately explains the creation flow, the important parameters to set, the risk of empty-shell creation, and what is returned. It doesn't enumerate defaults, but the schema already covers those.

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 coverage is 98%, so the baseline is 3. The description adds value by grouping key parameters (project_type/setting_brief/ethnicity/aspect_ratio, and consistency anchors cinematography_prompt/art_bible/visual_lock) and explaining why they matter, which goes beyond the individual schema descriptions.

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 states a specific verb and resource: '新建一部短剧(剧壳)', and clarifies the unique behavior of automatically creating N empty episodes and returning drama_id and episode_id. This clearly distinguishes it from the many generate_* sibling tools.

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?

It gives clear invocation context by strongly recommending that foundational settings be set at creation time, listing the key fields, and warning that a title-only shell causes rework. It doesn't explicitly name alternative tools, but the guidance is concrete and actionable.

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