Generate cohesive images for an entire site

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

No annotations are provided, so the description carries the full burden. It describes the local Draw Things dependency, local face/text detectors, and automatic retry, but does not detail error handling (e.g., if Draw Things is not running) or the outcome of verification failures beyond retry.

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 sentences, structured with the main functionality and a usage note. It is not overly verbose, but the first sentence is lengthy. It is well-organized but could be slightly more 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?

The tool has 4 parameters, no output schema, and no annotations. The description explains the process and constraints, but lacks details on output (e.g., folder and image naming conventions) and does not address potential side effects or prerequisites beyond the local server.

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 input schema has 100% coverage of parameter descriptions. The description adds minimal extra semantic value beyond what is already in the schema (e.g., defaults, constraints). The usage tip about maxPages is mentioned but not as part of parameter docs.

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 discovers pages for a site and generates folders with 16:9 and 9:16 cohesive images per page. It distinguishes itself from sibling tools like generate_page_image by focusing on an entire site.

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 mentions using a reasonable maxPages to control run time, but does not explicitly explain when to use this tool versus alternatives (e.g., generate_page_image for a single page). The context is implied but not clear.

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