workflow_import_pdfs

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the title extraction method (metadata then largest-font text), deduplication logic (skip identical file, attach to existing metadata-only entry), and storage copying behavior. It does not cover error handling or rate limits, but the provided details are substantial and clear.

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 numbered improvements, Args, and Returns sections. It front-loads the main purpose and key features. While slightly lengthy, every part contributes value and the organization helps readability.

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 0% schema coverage and no output schema, the description provides a detailed return structure and explains all parameters. It covers the core behavior (title extraction, deduplication, storage) and return value fields. Missing details like error handling for invalid paths are minor; overall, it is fairly complete.

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%, so the description must compensate. It does so by listing parameters in the Args section with context: pdf_paths (absolute paths), collection (exact case-sensitive, empty for root), and item_type (default 'preprint', with example values). This adds meaning beyond the schema's type and default fields.

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 it imports PDFs into Zotero with automatic title extraction and smart deduplication. It distinguishes itself from a related tool (zotero_add_from_file) by listing specific improvements, and sibling tool names indicate different workflows, making its unique purpose unambiguous.

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 a clear context for when to use the tool (importing PDFs) and mentions improvements over zotero_add_from_file, but it does not explicitly guide the agent on when not to use it or how it compares to sibling tools like workflow_get_paper or workflow_find_duplicates. The usage guidelines are implied rather than explicit.

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