list_annotations

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

No annotations are provided, so the description must carry the burden. It implies a read operation by stating '检查已有标注' (check existing annotations) and lists return values. However, it does not explicitly state that no data is modified, nor does it mention authentication or rate limits.

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 and structured with a purpose sentence followed by an Args section. It front-loads the main purpose and provides necessary details without extraneous text.

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 listing tool, the description covers the purpose, parameter, and return values. It also adds context about avoiding duplicates. With an output schema present, return details are adequately covered. Minor gap: no mention of error cases or path format requirements.

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 'item_id' is described as 'Zotero PDF 附件的 itemID（数字），或 PDF 文件的绝对路径' (Zotero PDF attachment itemID (number), or absolute path of PDF file), adding significant meaning beyond the schema's minimal type and title. Schema coverage is 0%, but the description compensates well.

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 '列出 PDF 附件上已有的所有标注' (list all existing annotations on PDF attachments), specifying the verb 'list' and the resource 'annotations'. It distinguishes itself from siblings like create_pdf_annotation and batch_annotate by being a read-only listing tool.

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 says '用于检查已有标注，避免重复标注' (used to check existing annotations to avoid duplicates), providing a clear use case. It also lists returned fields. However, it does not explicitly mention when not to use it or compare with siblings like get_pdf_layout_text.

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