zotero_get_recent

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

No annotations are provided, so the description carries full burden. It explains default behavior and parameter effects, but does not disclose any safety or behavioral traits beyond the basic read operation. It could be more explicit about what 'recent' means (e.g., time window) or any limitations.

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 two sentences, front-loaded with the core purpose, and every part is informative. No wasted words.

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) and the tool's simplicity (3 optional params), the description covers key use cases and parameter nuances. It lacks details on pagination or error handling, but those are minor for this tool type.

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?

With 0% schema description coverage, the description compensates well by explaining the meaning and allowed values for sort_by and item_type. The limit parameter is only mentioned with its default. The description adds value beyond the schema by providing usage context and examples.

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 clearly states the tool retrieves recently read, modified, or imported papers, using specific verbs and resources. It differentiates from sibling tools like zotero_search_items by focusing on recent items, and provides further detail on including notes.

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 on using parameters: default for papers only, item_type='' for notes, and sort_by options for different purposes. However, it does not directly compare to sibling tools like zotero_search_items, leaving some ambiguity about when to use this vs. alternatives.

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