batch_annotate

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

No annotations are provided, so the description must cover behavioral traits. It discloses that it is a write operation and requires closing Zotero. However, it does not mention idempotency, partial failure handling, rate limits, or the format of the return value (though an output schema exists). This leaves gaps in behavioral understanding.

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 no unnecessary words. It front-loads the main purpose in the first line, then provides a prerequisite, followed by a structured argument list that is easy to scan. Every sentence adds value.

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?

The description covers purpose, usage prerequisite, and parameter details adequately. However, it lacks information about the output (e.g., what is returned, success/failure per annotation) and any limitations like maximum batch size or error behavior. While an output schema exists, the description should at least hint at the return structure for completeness.

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?

Despite 0% schema description coverage, the description adds substantial meaning to both parameters. For 'item_id', it explains it can be a Zotero PDF attachment itemID (number) or an absolute PDF path. For 'annotations', it provides a clear template structure with fields like page_index, rects, color, etc., which is far beyond the bare schema type.

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 tool's purpose: '一次性创建多条 PDF 标注（减少调用次数）' (create multiple PDF annotations at once to reduce calls). It specifies the verb 'create', the resource 'PDF annotations', and the benefit of batching. This distinguishes it from the sibling tool 'create_pdf_annotation' which presumably creates single annotations.

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 provides a clear prerequisite: '写操作需要关闭 Zotero 桌面应用' (write operation requires closing Zotero desktop app). It implies when to use this tool (when creating multiple annotations to reduce calls) but does not explicitly state when not to use it or suggest alternatives like 'create_pdf_annotation' for single annotations.

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