top_items

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Retrieve top-level items,' with no mention of pagination, authentication, rate limits, or side effects. For a read operation, this is insufficient.

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 extremely short but not efficient; it lacks necessary information. It is not front-loaded with key details, and every sentence does not earn its place as there is only one vague sentence.

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 tool's complexity (many parameters, output schema exists), the description is vastly incomplete. It fails to explain what 'top-level items' are, how queries work, or any behavioral aspects. The contextual completeness is very low.

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%—the description does not explain any of the parameters. The tool has one required complex parameter 'req' with many nested fields (q, limit, sort, etc.), and the description adds no meaning beyond the schema. This is a critical 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 clearly states the action ('Retrieve') and the resource ('top-level items'), making it understandable. However, it doesn't specify what kind of items or the context (Zotero items), and the term 'top-level' might be ambiguous without background knowledge. It distinguishes itself from siblings like 'search_items' but lacks specificity.

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?

No guidance on when to use this tool versus alternatives like 'search_items' or 'collection_items_top'. No exclusions or context provided. The description is too minimal to guide the agent on appropriate usage.

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