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 fully covered. The description adds nothing beyond that — no note on pagination semantics, result ordering, empty result behavior, or external-system dependency — so it carries little extra behavioral weight.

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 short sentences, resource first, endpoint last — front-loaded and free of filler. It is terse rather than padded, though the terseness leaves coverage gaps rather than being a model of efficiency.

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 8 optional filters and no output schema, the description does supply the returned field list (number, date, status, type, totals), which partially compensates for the missing output schema. However it omits routing to acube_get_receipt_details for line-level detail and says nothing about how filters combine, leaving gaps for a listing tool with this many parameters.

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%, with every parameter documented including pagination defaults and the 'full page means there may be more' hint. The description adds no filter semantics of its own, so the baseline 3 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 resource (electronic commercial receipts / scontrini), the fields returned (number, date, status, type, totals) and the underlying endpoint GET /receipts, which together make the read/list purpose unambiguous. It does not distinguish this from sibling acube_get_receipt or acube_get_receipt_details, so an agent must infer the listing vs. single-record split from names alone.

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?

There is no explicit statement of when to use this tool versus the sibling receipt tools, nor any prerequisite, exclusion or filtering advice. The only usage signal is the implicit 'GET /receipts' listing.

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