zotero_get_feed_items

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

With no annotations, the description fully carries the burden. It states 'Read-only; does not trigger a new RSS fetch (Zotero desktop refreshes on its own schedule),' and that it returns a markdown list of titles, authors, dates, URLs. No contradictions.

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: one sentence per logical block (purpose, prerequisite, parameters, mode restriction, behavior, example). No wasted words, and key information is front-loaded.

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 presence of an output schema (not shown), the description adequately explains the return format (markdown list). It covers prerequisites, mode restrictions, safety (read-only), and provides an example, making the tool fully usable.

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 baseline is 3. The description adds value by clarifying that library_id is from zotero_list_feeds and NOT the feed's name or URL, which is not in the schema. Limit is described with default, matching schema. Structured parameter descriptions enhance understanding.

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 explicitly states 'Fetch recent items from a SPECIFIC Zotero RSS feed by its local library ID,' providing a clear verb-resource pair. It distinguishes itself from sibling tools like zotero_list_feeds by instructing the user to find the library ID first, ensuring no confusion.

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 gives explicit guidance: 'Find the right library_id first with zotero_list_feeds — guessing feed IDs never works.' It also specifies LOCAL MODE ONLY and that web mode returns a clear error, telling users when not to use the tool.

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