ppubs_download_patent_pdf

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

No annotations are provided, so the description carries the full burden. It discloses that the PDF is base64-encoded, that the return value is a dictionary, and that Claude Desktop may not display PDFs well. However, it does not mention error behavior for invalid/missing patent numbers, potential file size limits, or any other operational caveats, leaving a noticeable transparency gap.

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 compact and well-structured: a one-sentence purpose, a clear usage trigger, a brief note on display limitations, and concise args/returns sections. Every line adds useful information without unnecessary elaboration.

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 simple one-parameter download tool with an output schema, the description covers the essential invocation details, return format, and a practical display caveat. It lacks explicit differentiation from similar ppubs tools like ppubs_get_full_document, but the tool's scope is narrow enough that this is not a critical gap.

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 does so by specifying that patent_number should be provided 'without commas' and giving a concrete example ('7123456'), adding practical formatting meaning beyond the bare schema property. It could further clarify whether this is a US-only patent number, but the guidance is helpful for the single parameter.

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 opens with a specific verb+resource: 'Download a patent as PDF (base64 encoded).' It clearly identifies the tool's function and the output format, and 'official PDF document' distinguishes it from metadata/search sibling tools like ppubs_get_patent_by_number or patentsview_get_patent.

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 includes an explicit 'USE THIS TOOL WHEN: You need the official PDF document of a patent' statement, giving clear context for invocation. It does not name alternative tools or state when not to use it, but the when-to-use guidance is direct and sufficient for a simple download tool.

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