get_document_pdf_url

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

Since no annotations are provided, the description carries the full burden. It discloses that the URL is signed, short-lived, and requires no authentication. It also notes that drafts return an error. This covers the key behavioral traits adequately.

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 with three focused sentences. Each sentence adds value: purpose, return properties, and limitation. There is no redundant information.

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's simplicity and the presence of an output schema, the description covers the essential aspects: what it does, how the URL works, and the prerequisite of a finalized document. It could mention the output format but is sufficient for correct use.

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 100%, so the schema already documents both parameters. The description adds minimal additional meaning, only recontextualizing that the tool works for documents or receipts. It does not provide new details beyond the schema.

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 begins with 'Get a signed, shareable URL to a PDF render', clearly stating the verb and resource. It distinguishes from sibling tools by focusing on PDF URL generation, and the parameter documentation aligns with this purpose.

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 explains when to use the tool (to obtain a PDF URL) and provides important usage context: the URL is short-lived and does not require authentication. It explicitly states that drafts are not supported and advises to finalize first. However, it does not explicitly mention alternatives, though no sibling tools perform the same function.

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