get_pdf_text_bulk

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

Without annotations, the description covers key behaviors: extraction is pure text without coordinates, context usage is reduced by ~80%, and skip_refs defaults to true. However, it does not mention error handling for invalid item_ids or page ranges.

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 with purpose first, then differentiation, then workflow, then args. It is concise but the workflow section is slightly verbose. Overall efficient.

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 presence of an output schema, the description does not need to detail return values. It covers purpose, parameters, differentiation from siblings, and usage workflow adequately, making it complete for the agent's decision-making.

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 0%, but the description fully explains each parameter: item_id as Zotero itemID (number) or file path, pages as 0-indexed list with default of all pages, skip_refs as boolean to skip references with default true. This adds substantial meaning beyond the bare 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?

The description clearly states the tool extracts plain text from PDF pages without coordinates, specifically for large PDF content understanding. It distinguishes from the sibling get_pdf_layout_text by noting the absence of coordinates and reduced context usage.

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 specifies when to use this tool (bulk text extraction) and provides a recommended workflow: first use this for full text, then get_pdf_layout_text for coordinates on target pages, then create_pdf_annotation. Also mentions the difference from get_pdf_layout_text.

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