vibecloud_invoice_list

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

With no annotations, the description carries the behavioral burden. It explicitly says the operation is to 'read' and 'list' monthly invoices, signaling a safe, non-mutating call with no parameters. It does not describe pagination or output shape, but for a simple read/list alias this is a reasonable disclosure.

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 compact: two ideas expressed bilingually in four short clauses. The alias relationship is front-loaded and the function statement is immediate. No filler or redundant schema repetition is present.

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 parameterless list tool, the description is nearly complete: it names the object (monthly invoices), the scope (account), and the action (read/list). It leaves out output format and pagination details, but it points to cloud_invoice_list as the canonical definition, which offsets the need to restate them.

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 tool has zero parameters, so there is no parameter meaning for the description to add. The 100% schema coverage and empty properties make any parameter documentation unnecessary. The baseline for a no-parameter tool is 4.

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 specific verb and resource: 'List monthly invoices' and 'Đọc hoá đơn hàng tháng của tài khoản' (reads the account's monthly invoices). It also identifies itself as a compatibility alias of cloud_invoice_list, which is enough to distinguish it from the many sibling tools.

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 'Compatibility alias' implies that this tool is equivalent to cloud_invoice_list and can be used in its place, but there is no explicit when-to-use vs when-not-to-use guidance. It does not state whether an agent should prefer the canonical cloud_invoice_list or this alias in a given situation.

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