Get Recent Items

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

With no annotations, the description carries the full burden. It discloses the output ordering (dateAdded descending) which is useful. However, it does not mention important behavioral traits such as whether trash items are excluded, whether all metadata is included, or any potential limits beyond the schema. This is adequate but not rich.

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?

Three short sentences: purpose, use case, and ordering. Every sentence adds value, there is no filler, and the key information is front-loaded. This is exemplary conciseness.

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 tool with one optional parameter and no output schema, the description fully conveys what it does, why to use it, and how results are ordered. It is complete enough for an agent to invoke correctly without further clarification.

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) is fully described in the schema (default 10, max 50). The description adds no additional meaning about the parameter, so it does not elevate beyond the schema baseline. It does not compensate for anything because coverage is 100%.

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 identifies the tool as retrieving 'the most recently added items in the Zotero library,' which is a specific verb+resource+scope. It also notes the sorting order (by dateAdded descending), adding further precision. This distinct purpose separates it from sibling tools like search_items or get_item.

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 a clear use case ('Useful for checking what was recently imported or created'), which tells an agent when to invoke it. However, it does not explicitly mention alternatives or exclusionary cases, but given the unique scope, the context is sufficient. Thus it falls short of a 5 by not naming when not to use it.

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