zotero_get_recent

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

No annotations exist, so description carries full burden. It discloses ordering (dateAdded DESC), item types (all, including notes and attachments), and recommends client-side filtering for parent items. Lacks mention of error handling or rate limits, but otherwise thorough.

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?

Well-structured with front-loaded purpose, but some sentences could be condensed (e.g., filtering advice). Still clear and informative without redundancy.

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 2 simple parameters, an output schema exists (not shown but noted), and the description covers return behavior, alternatives, and filtering guidance. Complete for the tool's purpose.

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%, but description adds value: explains limit default, collection_key format (8-character), behavior when omitted, and provides example usage. This goes beyond schema descriptions.

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 it lists recently added items by dateAdded, with optional collection scoping. It explicitly distinguishes itself from sibling tools like zotero_semantic_search and zotero_get_collection_items, making the purpose unambiguous.

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 explicit guidance: use for 'what did I add recently?' questions, not for topic search or full collection retrieval. Names specific alternatives and mentions scope (active library, switchable with zotero_switch_library).

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