zotero_get_item_fulltext

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

No annotations provided, so description carries full burden. It discloses that long papers are truncated and suggests asking about specific sections, which is key behavioral info. Lacks explicit mention of being read-only or requiring PDF access, but 'Extract and read' implies non-destructive.

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?

Two sentences, front-loaded with verb and object. No wasted words. First sentence states core purpose, second adds usage guidance and a behavioral note.

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?

Has output schema but no annotations. Description provides basic purpose and truncation info but omits parameter explanations, preconditions (item must have PDF), and whether it's read-only. Adequate but not thorough for a 2-param tool.

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 has 2 parameters with 0% description coverage. Description does not explain item_key (required identifier) or max_chars (optional limit). Schema property names are somewhat self-explanatory, but the description should clarify them for reliable use.

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 it extracts full text from PDF papers, using specific verb 'Extract and read' and resource 'full text content from a PDF paper'. It distinguishes from sibling tools like zotero_get_item_metadata (which likely returns metadata/abstract) and search tools.

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?

Explicitly says 'Use when you need to analyze the actual paper content beyond the abstract', which guides when to invoke. Also mentions truncation for long papers, implying when to ask for sections. Does not explicitly exclude other use cases or mention alternatives, but context is clear.

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