Get gallery metadata

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the description's behavioral load is light. The description adds the maximum batch size (25), which is useful beyond annotations, but does not disclose rate limits, authentication needs, or the nature of the metadata structure. Given the rich annotations, a 3 is appropriate.

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 with clear structure: action, data fields, limit, and API source. It is front-loaded with the core purpose. No wasted words, but could be split into two sentences for readability.

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 a moderate parameter count (2), a complex input schema for galleries, and no nested objects. An output schema exists, so return value details are handled elsewhere. However, the description omits important context like the meaning of 'authoritative metadata', how to handle errors from the E-Hentai API, and how this differs from the sibling tool eh_get_gallery_metadata_batch. Adequate but leaves gaps.

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?

With 0% schema description coverage, the description bears full responsibility for parameter meaning. It mentions 'authoritative metadata' and lists output fields, implying the 'galleries' array parameter maps to gallery identifiers. However, it does not explain the 'site' parameter's role or the format of 'gid' and 'token'. The description adds some value but is incomplete.

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 specifies the verb 'Get' and resource 'gallery metadata', listing concrete data fields (namespaced tags, chain links, ratings, file size, torrent metadata) and a limit of 25 galleries. However, it does not differentiate from siblings like eh_get_gallery_detail or eh_get_gallery_metadata_batch, which likely overlap in 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 offers no guidance on when to use this tool versus its many siblings (e.g., eh_get_gallery_detail, eh_get_gallery_chain). There is no mention of prerequisites, exclusions, or context about the E-Hentai API's access restrictions. The sibling list includes multiple metadata-related tools, making this gap significant.

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