cloud_invoice_pdf

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

With no annotations provided, the description carries the full behavioral burden. It discloses the key behavioral trait: the PDF is written to a private temporary file, a path is returned, and the file may be cleaned up by the OS, so the caller must copy it elsewhere. This is meaningful transparency beyond a bare action.

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 one concise bilingual sentence with a clear order: action, output, and critical warning. Every element contributes value and the most important caveat about temporary-file cleanup is included without bloat.

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 single-parameter tool with no output schema and no annotations, this description covers the essential context: what is downloaded, where it is stored, what is returned, and what the caller must do before cleanup. It would be more complete if it noted how to obtain the invoice_id, but the core invocation contract is clear.

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. It does add some context by framing the operation as downloading an invoice PDF, implying invoice_id identifies the target invoice. However, it does not explain where invoice_id comes from or provide any format/lifecycle details, so compensation is minimal.

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 a specific verb and resource: download an invoice PDF to a temp file and return its path. It is easy to distinguish from listing tools like cloud_invoice_list, though it does not explicitly differentiate itself from the sibling vibecloud_invoice_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?

The description implies when to use the tool—when an invoice PDF needs to be downloaded—and includes the operational advice to copy the file before OS cleanup. However, it does not mention alternatives, exclusions, or how this differs from vibecloud_invoice_pdf.

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