Get highlights and comments on an item

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

Annotations already cover read-only and non-destructive behavior, and the description adds useful behavioral context: the returned annotation types, grouping by page, inclusion of comments, and ordering by page in a Markdown report. It does not contradict 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 concise and front-loaded with the core purpose, then cleanly organized into Args and Returns sections. Every sentence contributes meaningful information, including the colour usage note.

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?

For a read-only tool with one required parameter, the description covers all parameter semantics, the return format, and ordering. The presence of an output schema further reduces the need to detail return values.

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 input schema gives almost no parameter descriptions, but the Args section fully compensates: item_key clarifies parent item vs. attachment, annotation_type enumerates valid values, and colour explains hex format plus the coding-scheme use case.

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 states a specific action and resource: 'Retrieve the annotations stored on an item's PDF attachments.' It also distinguishes itself from siblings such as zotero_search_annotations by scoping retrieval to annotations on a specific item's PDFs.

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 clearly implies when to use the tool, but it never explicitly names alternatives or gives exclusion criteria. An agent must infer the difference between this and sibling tools like zotero_search_annotations.

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