zotero_collection_items

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'List the top-level items in a collection' without mentioning pagination (despite a 'limit' parameter), ordering, error handling, or access requirements. This leaves significant behavioral gaps.

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 a single concise sentence with no wasted words. However, it could be structured more helpfully (e.g., including parameter context), but given its brevity, it remains efficiently front-loaded.

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 tool with 2 parameters, no annotations, and an output schema (not shown), the description should specify what 'top-level items' means (e.g., excluding items in subcollections), mention pagination behavior, and clarify the required 'collection_key'. It does not do enough to be complete 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?

Schema description coverage is 0%, and the description does not explain either parameter ('collection_key' or 'limit'). The input schema provides titles but no descriptions, and the tool description adds no meaning beyond the schema, failing to compensate for the coverage gap.

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 'List the top-level items in a collection,' which clearly identifies the action (list) and resource (top-level items in a collection). It distinguishes from siblings like 'zotero_get_children' (which lists children of an item) and 'zotero_get_item' (single item retrieval), though not explicitly.

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 implies usage: when you need the top-level items of a specific collection. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'zotero_search' or 'zotero_get_children'), nor does it state 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.