get_item_fulltext

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

No annotations are provided, so the description carries the full burden. It adds useful context that Zotero indexes PDFs automatically when synced, implying fulltext may not be available otherwise. However, it does not disclose behavior when no fulltext exists, the return format (plain text vs. structured), or any error conditions. This is a read-only tool, so the missing details are not critical but still leave gaps.

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 two sentences long, front-loaded with the purpose, and every sentence adds value. The second sentence provides usage guidance without redundancy. It is appropriately sized for the tool's simplicity.

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 a simple read tool with no output schema and no annotations, the description covers purpose, usage, and a prerequisite. It does not explain edge cases like multiple attachments or missing fulltext, but the tool is straightforward and the description is sufficient for basic invocation. Slightly more detail on return format would make it stronger.

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 schema already provides 100% coverage of both parameters with descriptions (item_key and max_characters). The description adds no parameter-specific meaning beyond what the schema states, so the baseline of 3 is appropriate.

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's function: 'Get the full text content of a Zotero item's PDF attachment via Zotero's fulltext index.' It uses a specific verb ('Get') and resource ('full text content'), and distinguishes itself from likely siblings like get_items_details by emphasizing full-text reading rather than metadata/abstracts.

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 usage context: 'Use this to read the full content of papers instead of relying on abstracts.' It also notes a prerequisite ('Zotero desktop automatically indexes PDFs when synced'), which helps the agent know when the tool is appropriate. It does not explicitly name alternative tools or exclusions, 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.