zotero_recent

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

No annotations are provided, so the description carries the full behavioral burden. It does clarify that only top-level items are returned, which is useful, but it does not define what 'recent' means, describe ordering or pagination, or address whether the result is sorted by modification time. The Chinese phrase also claims added/modified while the English says modified, creating a transparency inconsistency.

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 short and front-loaded, with the core action stated immediately in both Chinese and English. The two sentences are redundant, but they do not waste much space. For such a simple tool, this level of conciseness is appropriate.

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 simple optional limit parameter and an output schema, the description is nearly adequate, but it leaves key contextual questions unanswered: how recent is 'recent', whether both additions and modifications are included, and what the default ordering is. The internal language mismatch also makes the exact scope unreliable for an agent.

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?

The single parameter 'limit' has no schema description and the main description does not mention it. With 0% schema description coverage, the description needed to compensate, but it adds no information about how the limit behaves or its relation to the result set. The parameter is self-explanatory from its name and default value, which prevents a score of 1.

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 states a specific operation: list recently modified top-level items in Zotero. It is clear and distinct from search/collection tools, though it does not explicitly contrast itself with siblings. The bilingual wording introduces a minor ambiguity between 'added/modified' (Chinese) and 'modified' (English), but the core purpose is still evident.

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?

There is no explicit guidance about when to use this tool versus alternatives like zotero_search or zotero_item. The use case is only implied by the word 'recently' rather than stated. No exclusions or alternative routing are provided.

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