acedatacloud_get_invoice

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

No annotations are provided, so the description must carry the transparency burden. It does disclose the caller-owned access scope and that it returns one invoice, which is useful, but it does not describe behavior for invalid IDs, not-found cases, or whether invoices in different statuses are returned.

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 short, front-loaded sentence with no wasted words. It immediately communicates the action, resource, and ownership scope.

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?

Given the tool's low complexity, one required parameter, and the existence of an output schema, the description conveys the main contract accurately. It does not explain behavior for missing IDs or non-owned invoices, but this is not essential for such a simple retrieval tool.

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 100%, so the invoice_id parameter is already documented as an Invoice UUID. The description adds the caller-owned context but no additional parameter-level detail, staying at the baseline for complete schema coverage.

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 'Get one caller-owned invoice' uses a specific verb and resource, and clearly limits the scope to a single caller-owned invoice. This distinguishes it from sibling tools such as acedatacloud_list_invoices, acedatacloud_get_order_invoice, and acedatacloud_get_invoice_download.

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 singular 'one' implies this is for fetching a specific invoice rather than listing invoices, but no explicit guidance is given about when to prefer it over related invoice tools. There is no mention of exclusions or alternatives.

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