create_pdf_annotation

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

No annotations provided, so description carries full burden. It discloses that this is a write operation requiring a closed Zotero and a refresh to see results, and that coordinates are from get_pdf_layout_text. No contradictions.

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?

Description is well-structured with summary, coordinate note, refresh note, warning, and parameter list. It is informative without being overly verbose; slightly more conciseness could be achieved but is already good.

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 complexity (7 parameters, 3 required) and no annotations, the description covers behavioral traits, parameter semantics, and side effects. Output schema exists but is not shown; description does not explain return value, but likely covered by schema.

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 Args section explains each parameter in detail: rects as coordinate arrays, color with hex examples, optional comment and text, and type with defaults. This adds significant meaning beyond 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?

Description clearly states the tool creates highlights/underlines on Zotero PDFs, which is specific and distinguishes it from siblings like get_pdf_layout_text (which returns coordinates) and list_annotations (which lists existing 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?

Provides context on when to use: after get_pdf_layout_text for coordinates, and includes important preconditions like closing Zotero desktop app and refreshing. Does not explicitly state when not to use, but the guidance is clear enough.

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