generate_episode_poster

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pay-per-use billing ('按用量后付'), which is useful, but it does not disclose whether generation is synchronous, what output is returned, whether it triggers follow-up jobs, or any side effects beyond the billing note.

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?

The description is short and front-loads the main purpose, which is good. However, the second fragment '图片步,按用量后付' is unclear and likely contains a typo, reducing the overall clarity and making the concise structure less effective.

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?

The tool has no output schema and no annotations, so the description should explain what the agent can expect after invocation. It does not mention return format, asynchronous behavior, or status checks. The billing note is helpful, but the overall description is incomplete for safe and correct invocation.

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 schema only provides episode_id as an integer greater than 0 with no description. The description's '某一集' clarifies that this ID refers to the target episode for the poster, adding meaning beyond the bare schema. However, it does not explain how to obtain the ID or what values are valid, and schema coverage is 0%.

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 clearly states a specific verb ('生成') and resource ('某一集' poster image), making the core function understandable. It also implicitly distinguishes this from sibling tools like generate_drama_poster by specifying episode-level scope. However, it does not explicitly contrast against similar poster/cover tools, leaving some ambiguity.

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 versus alternatives such as generate_drama_poster or generate_cover. The phrase '给某一集' implies an episode-specific use case, but no explicit context, prerequisites, or exclusion criteria are provided.

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