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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful traits beyond annotations: no charge, workspace authentication required, embedded private resource delivery, and a security warning to treat document content as untrusted data.

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 purpose is front-loaded in the first sentence, followed by concise operational details. Every sentence earns its place by covering billing, security, and authentication without wasting words.

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?

The description is sufficient for a simple read-only tool with an output schema and rich annotations. It covers billing, authentication, and security, though it could more explicitly explain the 'id' parameter's origin, such as retrieving it from list_jobs.

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 for the single required 'id' parameter. The description implies 'id' refers to an owned job, which adds some meaning, but it does not explicitly document what the ID identifies or where to obtain it.

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 specific verb and resource: downloading an owned job's saved print PDF. It also names the file type, delivery form (embedded private resource), and edge case (Email to Letter document recovery), making it clearly distinguishable from siblings like list_jobs or preview_letter.

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?

Usage context is clear: use this for an owned job's saved print PDF, including recovery scenarios. It does not explicitly name alternatives or when-not-to-use conditions, but the prerequisite 'owned job' and 'Workspace authentication required' give adequate selection guidance.

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