Get gallery image pages

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the output content and does not disclose external-site quirks, rate limits, or failure modes; however, it does not contradict 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?

One sentence, front-loaded with the action and the key scope limit. There is no filler or redundant restating of the title.

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?

An output schema exists and annotations cover the safety profile, so the description does not need to explain return values. The only notable gap is the lack of explicit sibling routing, but for a read-only single-page list operation with a fully documented schema, the definition is sufficiently 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?

The input schema documents 100% of parameters, including the gallery/galleryUrl mutual exclusivity, previewPage semantics, token pattern, and site enum. The description adds no parameter-level meaning beyond referring abstractly to 'one gallery preview page,' so the schema carries the burden.

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 uses a specific verb ('List') and names the exact resource: image-page numbers, page tokens, URLs, and preview thumbnails. The phrase 'from one gallery preview page' clearly scopes the tool and distinguishes it from the sibling eh_get_all_gallery_pages.

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 scope 'from one gallery preview page' implies when the tool should be used, but there is no explicit guidance about alternatives or when not to use it. An agent must infer that eh_get_all_gallery_pages would be the choice for multiple preview pages.

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