List recently added Zotero items

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

The description adds behavioral context by specifying the return format (Markdown list) and ordering (newest first). The annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat that. It adds useful details beyond the annotations.

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 concise, with a clear structure: a one-sentence overview, an Args section, and a Returns section. No unnecessary words or redundancy. It is front-loaded and easy to scan.

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 read-only list tool with one optional parameter and an output schema, the description covers all essential aspects: what it does, the parameter constraint, and the return format. It is complete for the tool's complexity, and the presence of an output schema means the return value details are handled elsewhere.

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 schema provides the limit parameter with a default but no description. The tool description adds the valid range (1-50), which is not present in the schema. This is valuable context for selecting a value, though it doesn't mention the default (which is in the schema).

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 action ('List') and the resource ('most recently added items in the library'). It is specific and distinguishable from sibling tools like zotero_search or zotero_get_item, even though it doesn't explicitly name alternatives. The purpose is 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?

There is no guidance on when to use this tool versus alternatives like zotero_search or zotero_get_collection_items. The description only states what it does, leaving the agent to infer the appropriate context. 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.