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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the account scope and the returned field set, but nothing about pagination limits, result ordering defaults, or rate behavior — a modest lift beyond the annotations rather than a rich one.

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?

Two dense sentences plus the endpoint, with the resource and returned fields front-loaded before the filtering clause. Nothing is redundant, though the field enumeration is long enough that it borders on a schema restatement.

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?

With 16 optional parameters and no output schema, the description usefully names the returned fields (uuid, number, date, document type, parties, amounts, marking/notification status) so the agent knows what a call yields. The only gap is absence of any note on pagination behavior or empty-result semantics, which is partly covered by the items_per_page schema text.

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 all 16 parameters are fully documented in the schema (defaults, enums, patterns, partial-vs-exact match semantics). The description only restates the filter categories at a higher level and adds no syntax or semantics beyond the schema, which is the correct baseline for a fully covered schema.

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?

Opens with a specific verb+resource ('Sent and received Italian e-invoices (SDI) of the account') and enumerates the fields returned, so the agent knows exactly what comes back. It implicitly separates itself from acube_list_draft_invoices and acube_get_invoice, though no sibling is named explicitly.

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 filter list ('Filter by date, number, document type, party name or VAT number') signals when the tool is applicable, but there is no explicit guidance on when to prefer this over acube_list_draft_invoices, acube_get_invoice, or acube_get_invoice_stats.

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