zotero_get_recent

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

Without annotations, description explains default behavior (papers only, sorting by dateModified) and how to modify it. Discloses that it returns recent items, but doesn't explicitly state it is read-only or mention pagination. Still, clear and consistent.

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 only; first sentence clearly states purpose, second sentence provides critical parameter guidance. No wasted words, front-loaded effectively.

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?

Covers main use cases and parameter behavior. Output schema exists so return details aren't needed. Could mention that results are a subset of library items, but overall adequate for a simple tool.

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 has 0% description coverage, but description adds meaning for sort_by and item_type (e.g., 'dateModified' for reading activity, 'dateAdded' for imports, default excludes notes). Doesn't explain limit, but its purpose is obvious.

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?

Description uses specific verb 'Get' and resource 'recently read, modified, or imported papers from your library', clearly distinguishing it from general search tools. The name 'get_recent' aligns with the behavior.

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?

Provides guidance on when to use different parameter values (e.g., sort_by='dateAdded' for imports, item_type='' for notes), but does not explicitly compare to sibling tools like zotero_search_items or mention when not to use this tool.

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