zotero_list_changes

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

With no annotations, the description carries the full disclosure burden and does so well: it reveals the return type (key -> version), the subject scope (item, collection, or search), and the incremental sync behavior. It stops short of describing limits/pagination or deletion semantics, but the output schema covers much of the return contract.

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?

Two sentences, no filler. The core behavior is front-loaded and the secondary usage guidance follows directly. Every clause contributes.

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 a low-complexity tool with two optional parameters, an output schema, and no annotation requirements, the description fully covers how to invoke and use the result. Nothing critical is missing for an agent 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 coverage is 100%, so the baseline is 3. The description adds value by explaining the since=0 sentinel and the recommended pattern of feeding the returned highest version back next time, which is not in 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 ('Track') and a well-defined resource ('changes since a version'), then states the concrete output shape ('returns key -> version for every item, collection, or search modified'). This is distinctive enough to separate it from list/delete/update sibling tools.

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?

It gives an explicit usage pattern: 'Use since=0 (or omit) for everything, and feed the returned highest version back next time.' It does not name alternatives, but no sibling exposes change tracking, so this is clear context rather than a gap.

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