zotero_get_item_fulltext

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

With no annotations, the description fully discloses behavioral traits: large output size, extraction paths (local SQLite, server-side index, direct download + PyMuPDF), limitations for scanned PDFs without OCR, and scope (active library only). 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?

The description is well-structured, front-loading purpose and warnings, then covering usage, parameter, scope, extraction details, and an example. It is slightly long but every sentence adds value, so a 4 is appropriate.

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 has an output schema (context signals indicate true), the description covers all necessary aspects: purpose, usage guidelines, parameter semantics, behavioral transparency, and limitations. No gaps are evident for an AI agent.

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_key is described in schema generically, but the description adds crucial meaning: it must be the parent item key (not attachment), and the tool locates the attachment itself. An example is provided, fully compensating for the schema's brevity.

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 returns full extracted text of a Zotero item's primary attachment. It distinguishes from siblings by explicitly naming alternatives for searching (zotero_semantic_search) and metadata retrieval (zotero_get_item_metadata). The warning about token size further clarifies its specific purpose.

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 explicit guidance on when to use (user wants to READ the paper), when not to use (searching or browsing), and lists alternative tools. Also advises against calling on multiple papers unless specifically requested. This gives clear decision criteria.

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