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

Annotations already declare this readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the fallback behavior (returning snapshot IDs when fewer than two exist) and pagination intent, but says nothing about result size, ordering, or what happens when from_id/to_id are omitted.

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?

Three tight sentences, each doing distinct work: core action, edge-case behavior, and alternative routing. Front-loaded with the primary purpose and free of filler.

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, so return formatting is fairly excused, and the fallback behavior is disclosed. However, with 5 loosely documented parameters and no explanation of how snapshots are selected or defaulted, the definition is not complete enough for an agent to invoke it confidently.

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 only 20%, and the description adds no meaning for from_id, to_id, corpus, or offset. The core mechanic — whether omitting from_id compares the latest two snapshots or defaults to something else — is left entirely unstated, which is the single most important parameter question for this tool.

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?

States a specific action and resource: paginating added/updated/deleted records between retained snapshots on this Omeka instance. The sibling list is large, and the description differentiates by naming the snapshot-comparison scope and pointing at search-tool alternatives, though it never says what 'retained snapshots' are.

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?

Gives two concrete routing rules: it lists snapshot IDs when fewer than two exist, and it directs agents to added_since on the search tools for recent additions without history. That is real when/when-not guidance, but nothing tells the agent how to choose between snapshots or which corpus defaults apply.

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