create_pdf_annotation

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

With no annotations provided, the description fully carries the burden. It discloses important behaviors: the operation modifies the PDF, requires a refresh/restart to become visible, and necessitates closing Zotero during write. This goes well beyond basic functionality.

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 well-structured with a clear purpose first, then usage notes, then parameter list. It is somewhat lengthy due to detailed parameter explanations, but every sentence adds value. A slight trim could improve 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?

The description covers the prerequisite (get_pdf_layout_text), the operation, and post-operation steps (restart/refresh). It also warns about the database lock. However, it does not describe the output or error handling, though an output schema exists.

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 coverage, the description explains each parameter in detail, adding meaning: item_id can be ID or path, rects come from get_pdf_layout_text, color with examples, and type default. This provides crucial guidance missing from the schema.

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 it creates highlight/underline annotations on Zotero PDFs. The verb 'create' and resource 'annotation' are specific, and it distinguishes from sibling tools like list_annotations or get_pdf_layout_text.

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 explicit context: coordinates should come from get_pdf_layout_text, and it warns about needing to restart or refresh after writing. It also advises closing Zotero to avoid database lock. However, it does not compare with batch_annotate or specify when not to use this tool.

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