Get every gallery image page

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

Annotations already provide readOnlyHint: true, openWorldHint: true, idempotentHint: true, and destructiveHint: false, so the safety profile is clear. The description adds that enumeration is serial (not parallel) and that images are not downloaded, which is useful behavioral context beyond the annotations. No contradictions are present.

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, concise sentence that front-loads the core action ('Serially enumerate every gallery preview page') and completes with essential distinguishing details. Every part earns its place with no wasted words.

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 an output schema (not shown but flagged 'true'), so return format documentation is not needed. The description lacks any guidance on parameter usage (which is partially compensated by the schema's defaults and structure), and it doesn't mention pagination or the serial enumeration's time cost. However, for a read-only enumeration tool with good annotations and an output schema, it is largely complete.

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%, meaning no parameter descriptions exist in the schema, so the description must compensate. However, the tool description does not explain any of the four parameters (site, gallery, maxImages, galleryUrl) – their meanings, defaults, or how they affect behavior. The description adds no value over the schema structure. Baseline for 0% coverage is lower than 3, but since maxImages and galleryUrl have reasonable names and defaults, a 3 is marginal.

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 verb 'enumerate' and the resource 'gallery preview pages', specifies that it returns a complete ordered list without downloading images, and distinguishes this from sibling tools like 'eh_get_gallery_pages' (which likely gets page content) and 'eh_get_image_page'. The scope of 'all gallery pages' is unambiguous.

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 implies use when you need the full ordered list of preview pages without downloading images, but it does not explicitly state when to use this versus 'eh_get_gallery_pages' or 'eh_get_image_page'. No exclusions or conditions are provided, though siblings with similar names suggest the need for differentiation.

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