Get salesbook PDF

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be safe. The description adds valuable context beyond annotations: it states the download returns a base64-encoded string and mentions the optional save_path behavior, which informs expected output handling. The endpoint path is also included, which is extra useful context.

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 extremely concise: three short lines with zero filler. The first line restates the title but the second line provides the actionable definition, and the endpoint line adds precise reference. Every sentence earns its place.

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 no output schema, the description adequately explains the returned format (base64) and the optional save-path behavior. Missing are potential error conditions or notes on file size limits, but these are not critical for basic invocation. The main gap is the lack of usage-versus-alternative guidance.

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 input schema has 100% description coverage, so all three parameters are already self-documenting. The description does not add new meaning to the parameters, though the base64-encoding mention indirectly clarifies the output related to save_path. 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 clearly states the action ('Download the PDF file attached to a salesbook invoice') and the resource (salesbook invoice PDF). It distinguishes this from sibling PDF tools like get_sales_invoice_pdf and get_quotation_pdf by explicitly referencing 'salesbook invoice'.

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?

No guidance is provided about when to use this tool versus the many sibling PDF retrieval tools (e.g., get_sales_invoice_pdf, get_purchase_invoice_pdf). The description assumes the agent already knows it should be used specifically for salesbook invoices, without explicitly stating selection criteria or excluding alternatives.

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