quote_scene_images

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly states '零扣费' (zero deduction), clarifying that this quote does not consume points, and lists the returned fields. It does not explicitly say it performs no generation, but '报价' and 'estimated_points' strongly imply a non-mutating quote operation.

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 a single compact sentence that front-loads the core purpose ('报价'), then gives the scenario, return fields, and billing behavior. Every element earns its place with no 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 low-complexity tool with one parameter and no output schema, the description covers purpose, usage context, response fields, and billing behavior. It could optionally mention how quote_id relates to a follow-up generation call, but nothing essential is missing for an agent to invoke it correctly.

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 0%, and the description never mentions drama_id or explains how it is used. The parameter name is self-explanatory, but the description adds no parameter-level meaning and does not compensate for the low schema coverage.

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 immediately states this is a quote operation ('报价') for batch-generating scene images for scenes missing images, which clearly distinguishes it from generate_scene_images and other quote_* siblings. It also names the concrete return fields, leaving no ambiguity about what the tool does.

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 gives a clear use context: use it when you need a cost quote for batch scene-image generation for scenes that lack images. It does not explicitly name alternatives or exclusions, but the sibling tool names (generate_scene_images, quote_frames, etc.) make the intended differentiation inferable.

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