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

The annotations already declare that this is a read-only, non-destructive, open-world operation, so the description does not need to establish safety. It adds useful context by stating that the response includes FatturaPA JSON content and by naming the underlying GET endpoint, but it does not describe error behavior, permissions, or response shape in more detail.

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 compact clauses with no wasted wording, and the core resource plus lookup key is front-loaded. The endpoint reference is supplementary but still brief.

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 one-parameter read tool with complete schema coverage and annotations covering safety, the description is largely complete. It notes the returned FatturaPA JSON content, which matters because no output schema is provided, though it could mention error behavior or the origin of the uuid.

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 single uuid parameter is already fully documented in the input schema. The description repeats that lookup is by uuid but adds no format, source, or validation detail beyond the 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?

The description states a specific verb and resource: retrieve one draft invoice by uuid, including its FatturaPA JSON content. It distinguishes draft invoices from the sibling get_invoice by naming the draft resource, but it does not explicitly contrast the two alternatives.

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 'by uuid' implies this tool is for direct lookup when the caller already has a draft invoice identifier. However, it does not explicitly say when to use this instead of acube_list_draft_invoices or acube_get_invoice, nor does it mention prerequisites such as obtaining the uuid first.

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