Save Pdf

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

The annotations already indicate a write operation (readOnlyHint=false) and potentially destructive behavior (destructiveHint=true). The description adds the 'authorized local server path' constraint, implying permission requirements. However, it does not disclose whether existing files are overwritten or what happens on failure, so the added transparency is modest.

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 a single, front-loaded sentence with no unnecessary words. It conveys the core action and destination efficiently, earning top marks for conciseness and structure.

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 potentially destructive write operation with an optional parameter, the description lacks critical behavioral details such as overwrite semantics, the scope of 'authorized' paths, and the selection logic when multiple attachments exist. The presence of an output schema does not compensate for these gaps, leaving the description incomplete.

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 has 0% description coverage, and the description does not explain item_key, save_path, or attachment_key. The phrase 'a Zotero PDF' loosely implies item_key identifies the item, but the role of attachment_key (e.g., selecting among multiple PDF attachments) is entirely undocumented, making this insufficient compensation.

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 action ('save'), a specific resource ('a Zotero PDF'), and a destination ('an authorized local server path'), which distinguishes it from sibling tools like download_pdf that save to a local client. However, it does not explicitly differentiate from alternatives, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus sibling tools such as download_pdf, attach_file, or save_bibtex. No prerequisites, exclusions, or context for choosing this tool are provided, leaving the agent without usage direction.

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