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

The annotations already establish that this is a non-destructive, idempotent read operation. The description adds meaningful behavior beyond that: the output is a link the person opens, and the file itself is not transmitted through the conversation.

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 short and front-loads the key output behavior in the first sentence. The API endpoint and documentation URL are useful context, though the fragmentary first sentence is less polished than it could be.

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 one-parameter read operation with an output schema and full annotation coverage, the description supplies the essential missing context: the return is a link rather than file content. It could be slightly more complete by naming the relevant alternative for reading the PDF internally.

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% for the single DocumentNumber parameter, so the schema already explains that it identifies the offer. The description reinforces this indirectly via the API path but does not add substantial parameter-level guidance 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 makes clear that the tool returns an offer as a PDF and specifically as a download link, not a file in the conversation. It identifies the resource well but does not explicitly differentiate from nearby siblings such as read_offer_pdf or list_offers.

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?

It implies the usage scenario by saying the link is opened by a person to download the file and that the file never passes through the conversation. However, it does not explicitly say when to choose this over read_offer_pdf or other PDF-related siblings.

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