Get quotation PDF

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds behavioral detail by specifying that the PDF is returned as a base64-encoded string, which is valuable and not present in the 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 very short and to the point. The first line repeats the title, but the following sentences add value by explaining the output format and the endpoint. It is efficient without unnecessary fluff.

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 read-only download tool with full schema coverage and supportive annotations, the description is complete enough. It explains the output format (base64) and clearly identifies the resource, so an agent can invoke it correctly without additional details.

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 already provides 100% description coverage for all three parameters. The description mentions base64 encoding, which relates to the save_path parameter, but does not add detailed syntax or default behavior beyond the schema. Baseline 3 is appropriate.

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 clearly states the verb 'Download' and the resource (PDF of a quotation) plus the output format (base64-encoded string). It distinguishes itself from sibling tools like get_sales_invoice_pdf or get_purchase_invoice_pdf by naming the specific entity type.

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 provides clear context on what the tool does and implies when it would be used (whenever a quotation PDF is needed). It does not explicitly list exclusions or alternatives, but the purpose is specific enough that an agent would not confuse it with other PDF getters.

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