vibecloud_invoice_pdf

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

No annotations are provided, so the description carries the full disclosure burden and meets it well: it discloses the private-temporary-file destination, states that a path is returned, and warns that the file must be copied to a persistent location before the OS cleans it up. These are precisely the behavioral traits an agent needs to use the tool safely.

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 front-loaded with the alias disclosure and covers function, return type, and the cleanup caution in a few lines. The Vietnamese/English duplication doubles length but serves locale compatibility; no sentence is filler.

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 download tool with no output schema and no annotations, the description covers the essentials: destination (private temp file), return value (path), and a critical lifecycle warning (copy before OS cleanup). It does not state where to obtain invoice_id (e.g., from an invoice_list tool) or error behavior, which would round it out.

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% and the description does not explain invoice_id beyond the tool's overall purpose. However, with a single required parameter whose name is self-describing and whose role is strongly implied by 'download invoice PDF', the practical gap is small. No format, source, or validation semantics are added.

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 states a concrete verb+resource pair ('Download invoice PDF to a private temporary file') and the return value (a path). It also immediately declares itself a compatibility alias of cloud_invoice_pdf, which clearly distinguishes it from the sibling set and tells the agent exactly what this tool is.

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 bilingual statement 'Compatibility alias' of cloud_invoice_pdf explicitly establishes interchangeability with the original tool, which is the relevant usage context for an alias and routes the agent correctly among siblings. It lacks an explicit when/when-not condition, but for an alias the declaration itself is the routing guidance.

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