cloud_invoice_pdfDownload an invoice PDF to a private temporary file and receive its path. Copy the file to a permanent location before the OS deletes it.
Tải PDF hoá đơn vào file tạm riêng tư, trả path; sao chép ra nơi cần giữ trước khi hệ điều hành dọn. / Download invoice PDF to a private temporary file.
| Name | Required | Description | Default |
|---|---|---|---|
| invoice_id | Yes |
Changes observed during successful MCP inspections.
v0.11.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real behavior: the returned path points at a private temp file that the OS will later clean up, and the caller must copy it out to persist it. That ephemerality warning is genuinely valuable context beyond the annotations.
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?
Short and front-loaded, with the core action first and the temp-file warning second. The bilingual duplication doubles the text length, which is mildly wasteful but serves locale needs.
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 download tool with no output schema, the description covers the return value (a path) and its lifecycle behavior. What remains missing is the invoice_id format and confirmation that the payload is a path rather than bytes.
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?
With one parameter and 0% schema description coverage, the description must carry the load; it never explains invoice_id at all. The name is self-explanatory and the invoice context is clear, but no format or source hints are given.
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?
States a specific verb+resource: 'Download invoice PDF'. The bilingual phrasing makes the action unambiguous. It does not distinguish itself from its near-identical sibling vibecloud_invoice_pdf, so it stops short of a 5.
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?
Usage is implied by the single required invoice_id, but the description never says when to reach for this versus cloud_invoice_list or vibecloud_invoice_pdf. The only actionable guidance is about post-call file handling, not tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.