getSubscriptionInvoicePdf

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

With no annotations, the description carries the burden of behavioral disclosure. It states the operation is read-only, shows the HTTP method (GET), and discloses a rate limit of 100 requests per 1m. These are meaningful behavioral details, though it does not cover auth requirements or error behavior.

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 entire description is one dense, front-loaded sentence containing the action, resource, endpoint, rate limit, and read-only nature. There is no filler or redundant repetition.

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 one-parameter read-only download with no output schema, the description is largely complete: it names the resource, the endpoint, the rate limit, and the fact that the result is a PDF. It lacks only minor context such as authentication expectations or how to obtain the invoiceId, but this does not seriously impair usability.

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 0%, so the description must compensate for the undocumented invoiceId parameter. It does not explain what invoiceId represents, where to obtain it, or its format; it appears only in the endpoint path. The parameter name is self-explanatory, but the description adds no semantic value 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 uses a specific verb ('Download'), a precise resource ('branded PDF of the tenant's own platform subscription invoice'), and an explicit endpoint. This clearly distinguishes it from sibling list/get tools, which focus on data objects rather than PDF downloads.

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 phrase 'tenant's own platform subscription invoice' gives clear context for when this tool applies, and the endpoint path '/paygate/me/invoices/{invoiceId}/pdf' reinforces the scoping. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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