Download Pdf

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds that the output is a 'remote-safe MCP resource link', which clarifies the return type and that it is intended for use with other tools. This is a useful behavioral trait beyond annotations.

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 concise and front-loaded with the core purpose. The args list is clean and structured, with no unnecessary words. Every sentence adds value.

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 tool is a simple read operation with robust annotations and an output schema, the description sufficiently covers purpose, usage context, and parameter semantics. An agent can confidently select and invoke this tool.

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%, but the description fully compensates by clearly explaining both parameters: item_key must be the parent item (not the attachment), and attachment_key is optional for multiple PDFs. This level of detail is essential for correct invocation.

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 the tool 'Return a PDF as a remote-safe MCP resource link', which is a specific verb and resource. It clearly distinguishes from text-based retrieval tools by emphasizing the PDF link output and the 'remote-safe' aspect.

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?

It explicitly says 'Useful when Zotero's fulltext index is incomplete (e.g. for books) and you need to read the PDF directly with other tools.' This provides clear context for when to use, and implies the alternative is fulltext retrieval, though it does not name a specific sibling tool.

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