Get every gallery image page

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

Beyond the annotations (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), the description reveals meaningful behavioral traits: serial enumeration, complete/ordered output, and no image downloads. These traits help an agent set expectations about performance and side effects. There is no contradiction with the annotations.

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?

A single sentence that front-loads the core behavior and constraints with no filler. Every phrase contributes: 'serially', 'every gallery preview page', 'complete, ordered image-page list', and 'without downloading images'.

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?

Given the rich output schema and annotations, the description adds the essential behavioral context an agent needs to select and invoke the tool correctly. It clearly states what the tool does, how it behaves, and what it avoids, leaving parameter details to the schema.

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 baseline is 3. The description adds no additional meaning about parameters like site, gallery, maxImages, or galleryUrl; it relies entirely on the schema for parameter semantics.

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 a specific verb ('enumerate'), resource ('every gallery preview page'), and result ('complete, ordered image-page list'), plus a scope constraint ('without downloading images'). It does not explicitly differentiate this from the sibling eh_get_gallery_pages, though the 'every' phrasing implies broader coverage.

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 conveys a clear usage context: use this when you need a complete, ordered enumeration of gallery image pages without downloading the images themselves. However, it does not explicitly name alternatives or state when not to use it, so it falls short of explicit routing guidance.

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