Resolve gallery from image page

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

The description discloses the core transformation behavior (input to output). Annotations already provide readOnlyHint, idempotentHint, and openWorldHint, so the bar is lower. The description adds the context of what the tool produces (gallery ID and token), which is beyond 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?

The description is a single sentence of 18 words, perfectly concise and front-loaded. Every word earns its place with no redundancy.

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 tool has 3 parameters including a nested object and an enum, and an output schema exists, the description is minimal. It covers the basic input-output mapping but lacks details on the two modes of operation (URL vs. page reference), the site parameter, and error handling. The output schema may compensate, but the description itself is not fully 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% (no top-level parameter descriptions), so the description must compensate. It mentions 'image-page URL or page reference' which maps to pageUrl and page, but does not elaborate on the page object structure, the site enum, or the relationship between parameters. The schema provides nested descriptions, but the tool description adds only marginal value.

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 specific verb 'Convert' and the resource 'image-page URL or page reference into gallery ID and token'. It distinguishes from sibling tools like eh_resolve_gallery_batch by implying single resolution, and the title reinforces the purpose.

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 the tool is for resolving a gallery from an image page, but it does not explicitly state when to use it versus alternatives like eh_resolve_gallery_batch or other lookup tools. There is no guidance on prerequisites or exclusions.

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