Compare gallery versions

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

Annotations already establish this as safe, read-only, idempotent, and non-destructive. The description adds useful behavioral detail by specifying exactly which attributes are compared, including namespaced tag additions/removals, without contradicting 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 efficient sentence with no filler. The core verb and resource appear first, followed by the comparison dimensions, and every word contributes meaning.

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 is a read-only comparison with an output schema, fully documented parameters, and annotations covering safety and idempotency. The description plus structured metadata gives an agent everything needed to call it correctly.

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 100%, with before/after and site all documented in the schema. The description adds no parameter-level detail, so the baseline of 3 is appropriate; it neither helps nor hurts beyond the schema.

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 ('Compare'), a clear resource ('two gallery versions'), and enumerates the exact dimensions compared (title, posted time, page count, file size, tag changes), making the tool's purpose unmistakable and distinct from sibling tools like eh_find_latest_gallery_version or eh_get_gallery_chain.

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 states what the tool does but gives no guidance on when to choose it over alternatives such as eh_get_gallery_chain or eh_find_latest_gallery_version. There are no explicit use cases, exclusions, or context for selecting this tool.

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