zotero_recent

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

No annotations are supplied, so the description carries the disclosure burden. 'List' implies a read-only operation, and 'most recently added or modified' hints at date-based ordering, but it does not state sorting direction, return format, or side-effect behavior explicitly. Adequate but minimal.

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?

A single, front-loaded sentence states the operation, and the em-dash adds a relevant use case without filler. Every word earns its place.

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 simple optional-parameter list tool, the description plus the richly detailed input schema is nearly complete: the agent knows what it lists and which use case it serves. Because there is no output schema, an explicit note on returned item shape or 'newest first' ordering would make it fully complete.

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 description coverage is 100%, and the schema already explains 'by', 'limit', 'source', and 'library' in detail, so the baseline is 3. The description only loosely maps to the 'by' parameter ('added or modified') without adding deeper semantics.

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 opens with a specific verb and resource: 'List the most recently added or modified references'. This clearly identifies a recency-based listing operation and differentiates it from siblings like zotero_search and zotero_fulltext_search, which are query-oriented rather than recency-oriented.

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 phrase 'useful for "what have I saved lately"' gives a concrete, appropriate context for invoking the tool. It does not explicitly mention when not to use it or name alternatives like zotero_search, so it falls just short of a 5.

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