describe_images_in_folder

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

With no annotations, the description carries the full burden. It discloses parallel execution and speed ('并行识别，速度较快'), which are useful behavioral traits. However, it does not explicitly mention read-only safety, file format requirements, or failure modes, leaving some gaps.

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 three concise sentences, each earning its place: purpose, use case, and performance trait. It is front-loaded and free of fluff.

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 batch read tool with fully documented parameters and an output schema, the description sufficiently covers purpose, usage, and performance. Minor gaps like error handling are acceptable given the structured fields and simple read-only nature.

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 100%, so the schema already documents all parameters. The description adds context about batch scanning but does not enhance understanding of individual parameters beyond what the schema provides (e.g., limit default is already in the schema). Baseline 3 is appropriate.

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 the tool's function: scans all images in a folder, recognizes them in parallel, and returns a description for each. It also distinguishes from sibling tools (describe_image, describe_pasted_images) by focusing on folder-based batch analysis.

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 explicitly states the tool is suitable for recognizing multiple images at once (e.g., putting screenshots in a folder for batch analysis), giving clear when-to-use context. It does not explicitly name alternatives, but the contrast with single-image tools is implied.

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