Get metadata for many galleries

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

The description adds significant value beyond the annotations. It reveals that the server splits requests into official 25-item API batches and preserves input order—key behavioral details not covered by readOnlyHint, openWorldHint, idempotentHint, or destructiveHint 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 two efficient sentences with no wasted words. It front-loads the core purpose ('Get official metadata for up to 500 galleries') and adds necessary technical detail about batching and order preservation in the second sentence.

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's moderate complexity (only 2 parameters, none nested), the presence of an output schema, and rich annotations, the description is complete. It covers the key behavioral aspects (batch size, splitting behavior, order preservation) that neither the schema nor annotations address.

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 schema has 0% description coverage, so the description must compensate. It does not detail the two parameters (site and galleries) beyond the schema, but the tool's purpose and batch behavior are sufficiently clear. The description raises the score above the baseline of 3 for 0% coverage, but stops short of explicitly explaining each parameter's role.

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 the verb 'Get' with a specific resource ('official metadata for many galleries') and clearly states the batch size limit of 500. It distinguishes from its nearest sibling, eh_get_gallery_metadata, which is the single-item version, by explicitly mentioning batch processing.

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 when to use this tool: when you need metadata for up to 500 galleries in a single call, leveraging automatic batching. However, it does not explicitly state when not to use it (e.g., for fewer than 500 items, eh_get_gallery_metadata might suffice) or mention alternative tools for different needs.

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