cloud_invoice_list

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

With no annotations, the description carries the behavioral burden. The verb 'List' / 'Đọc' does communicate a read-only operation and 'monthly invoices' scopes the subject matter, but the description does not disclose pagination, ordering, filtering behavior, or the shape of the returned invoice list.

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 two short clauses, action-first, with no filler. The Vietnamese and English versions are near-duplicates, but bilingual clarity is acceptable for a multilingual MCP agent and the overall size is appropriately minimal.

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 zero-parameter listing operation, the description is sufficient to convey the intended call and the general result: a list of monthly invoices. It omits return-field details, but that is acceptable given the simplicity and the absence of an output schema.

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?

The input schema has zero properties and full coverage, so there are no parameter semantics to explain. The description adds no parameter details, but none are needed for a zero-parameter tool; the 0-parameter baseline of 4 applies.

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 names the action ('List' / 'Đọc') and the resource ('monthly invoices' / 'hoá đơn hàng tháng') with account scope. It is clear about what the tool does, though it does not explicitly distinguish itself from vibecloud_invoice_list or cloud_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 the obvious use case: listing monthly invoices for the account. It provides no explicit guidance about when not to use it or which sibling tool to select instead, such as cloud_invoice_pdf for PDFs or vibecloud_invoice_list for the VibeCloud platform.

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