zotero_create_annotation

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

No annotations are provided, so the description carries the transparency burden. It discloses the return value ('Returns the new annotation's key'), the required PDF-coordinate placement format, and the critical attachment-key requirement. The mutating nature is obvious from 'Create,' and the description adds meaningful behavioral context beyond that.

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?

Three focused sentences front-load the purpose, then give the position format, attachment-key guidance, and return value. No filler or repetition; every sentence earns its place.

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 an 8-parameter tool with a nested position object and an output schema, the description covers the essential call semantics: annotation types, position format, attachment target, and return value. Optional parameter behaviors are already documented in the input schema, so the description is reasonably complete. It could add explicit notes about which parameters apply to each annotation type, but the schema partially covers that.

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 coverage is 100%, so the baseline is 3, but the description adds real value on top: annotation_position gets a concrete JSON example and coordinate-system clarification, and attachment_key is disambiguated with the 'not the parent item' warning. This goes beyond what the schema alone provides.

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?

States a specific verb and resource: 'Create an annotation on a PDF attachment' and enumerates the four supported kinds (highlight, note annotation, image, ink). This clearly distinguishes it from sibling tools like zotero_create_note, which creates a standalone note rather than a PDF annotation.

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?

Gives clear operational context by saying 'Attach to the ATTACHMENT key (the PDF), not the parent item,' which prevents a common misuse. It does not explicitly contrast with alternative sibling tools, but the PDF-attachment framing is enough for an agent to infer when this tool applies.

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