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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered without the description's help. The description earns some credit by naming the fields returned (line items, VAT, discount, taxable totals), which matters because there is no output schema, but it says nothing about not-found behavior or how the payload differs from acube_get_receipt.

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 with the returned payload front-loaded before the endpoint reference; nothing is padded. It could have spent one of those sentences on sibling differentiation instead of repeating the route, but it is efficiently structured.

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 one-parameter read tool, the description gives a reasonable sketch of the return content in lieu of an output schema. The material omission is the relationship to acube_get_receipt, which a 'details' variant of the same resource should really explain.

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?

There is a single uuid parameter with 100% schema description coverage, and the schema already tells the agent to source it from acube_list_receipts. The description adds no format, length, or sourcing detail beyond that, so 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 states a specific payload verb+resource: it returns line items and VAT/discount/taxable totals for one receipt, plus the underlying route GET /receipts/{uuid}/details. It is clear on its own, but it never distinguishes itself from the sibling acube_get_receipt, leaving an agent to guess which receipt endpoint returns which shape.

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 statement of when to use this versus acube_get_receipt or a receipt list call. The only workflow hint lives in the schema ('from acube_list_receipts'), not the description, and no exclusions or prerequisites are given.

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