Save Pdf

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not restate write behavior. The description adds the 'authorized local server path' detail, which is a useful contextual nuance about where saving is permitted. However, it does not disclose side effects like overwriting existing files or error behavior. Given the annotations cover the core safety profile, a 3 is appropriate.

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 concise sentences with no filler. The key instruction (save a PDF) is front-loaded, and the library-targeting guidance is clearly separated. Every sentence adds value and the length is appropriate for the scope.

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?

With 5 parameters, 0% schema coverage, and no alternative tool guidance, the description is incomplete. It leaves item_key, save_path, and attachment_key unexplained, which are essential for a successful call. The output schema exists but the description doesn't hint at return values or outcomes. Given the complexity, the description is not sufficient for an agent to understand all required inputs.

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 description coverage is 0%, so the description must compensate. It explains the pairing requirement and default behavior for library_id and library_type, which is genuinely helpful, but it completely ignores item_key, save_path, and attachment_key. These are required or commonly used parameters, and the description offers no guidance on what they mean or how they should be formatted. The description only adds value for two of five parameters.

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 states a clear, specific action: 'Save a Zotero PDF to an authorized local server path.' This is a concrete verb+resource combination, and it distinguishes the tool from siblings like save_bibtex (which saves bibliography data) and download_pdf (which likely retrieves, not saves). No ambiguity about what this tool does.

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 gives parameter-level guidance ('Pass both library_id and library_type to target another library; omit both to use the configured default') which helps with invocation, but it does not explicitly state when to prefer this tool over alternatives like save_bibtex or attach_file. Usage context is implied by 'Save a PDF' but no alternatives are mentioned or exclusions provided.

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