get_color_scripts

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

With no annotations, the description carries the behavioral burden. It explicitly labels the operation as a read ('读') and states a precondition: the color script must already have been generated. It also notes the operation is free ('免费'). This is good transparency for a read-only tool, though it does not describe failure behavior when no script has been generated.

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 two short sentences with no wasted structure. The core purpose is front-loaded, and the supplementary sentence adds useful contrast with the generation sibling. '免费' is extra but not harmful and still concise.

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 read-only tool with no output schema, the description provides the essential information: what it reads, for which scope, and that a prior generation step is required. It does not describe the return format, but that is less critical when the operation is a simple fetch and the resource is already defined.

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 has 0% description coverage and the description does not explain drama_id. However, the description's use of '该剧' (the drama) ties the single parameter to the target resource, and the parameter name is self-explanatory. Some compensation is present, but it does not explicitly describe the parameter or its constraints.

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 begins with a clear verb '读' (read) and a specific resource '色彩脚本' (color script), scoped to a drama ('该剧'), with a parenthetical clarifying what the color script is ('全片配色情绪'). It also explicitly contrasts with the sibling generate_color_script, making the tool's role unmistakable.

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?

The description states that generate_color_script creates the script while this tool reads it, which clearly implies this is the retrieval counterpart to generation. It does not spell out a full 'use X when... not when...' rule, but the contrast is direct and sufficient for a simple getter.

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