quote_character_portraits

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

With no annotations, the description carries the behavioral burden and does disclose a key trait: '零扣费' (zero deduction). It also signals this is an estimation operation by listing estimated_points and quote_id as outputs, and explains why the portraits matter for identity consistency.

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 compact and front-loaded with the core verb and resource. The return fields, zero-cost note, and recommendation are each given in one short phrase, with no redundant filler.

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 quote tool with no output schema, this is minimally adequate: it explains purpose, zero cost, and return field names. But it leaves episode_id semantics and the meaning/use of quote_id ambiguous, and it does not explicitly say that no actual generation happens.

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 provides 0% description coverage for the only parameter, episode_id, and the description never mentions it. While the name is mildly self-explanatory, the description does not clarify that the quote applies to the characters within that episode or how the episode_id is used.

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 opens with '报价' (quote) and a specific resource: batch-generating character portraits for characters missing them. This clearly separates it from generation tools like generate_character_portraits and from other quote tools such as quote_scene_images or quote_videos.

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 states a clear use context: quote before generating videos, for characters lacking portraits, and highlights that calling it costs zero points. It does not explicitly name alternative tools or when-not-to-use, but the context is strong enough for tool selection.

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