get_quote_pdf

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

The description adds no behavioral context beyond what the annotations already provide. It does not disclose whether the PDF is returned as a file, URL, or base64, nor any details about authentication, rate limits, or the effect of the logopaper parameter. The description merely repeats the tool's basic function.

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?

While 'Show PDF' is concise, it is under-specified to the point of being unhelpful. It is a fragment rather than a proper description, and it does not structure information in a way that aids the agent. It is not a case of efficient writing but of missing substance.

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 tool has no output schema, so the description should have explained the return value or content of the PDF, but it does not. The description is too minimal to be considered complete even for a simple tool, especially with the logopaper parameter whose effect is only partially explained.

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% and both parameters (quote_id, logopaper) have meaningful descriptions in the schema. The description itself adds no parameter details, but since schema coverage is high, the baseline of 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 'Show PDF' is extremely vague and essentially restates the tool name 'get_quote_pdf' without adding any specificity. It does not clearly state that this fetches a PDF for a quote or what makes it distinct from other PDF-related tools like get_invoice_pdf or get_order_pdf.

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?

There is no guidance on when to use this tool or when to use an alternative. It does not mention any prerequisites, context, or exclusions, leaving the agent to guess based solely on the name.

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