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 underlying endpoint and that receipts may be printed or digital, but says nothing about ordering, whether all account receipts are returned, or what the response shape looks like.

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?

Three terse fragments with the resource stated first and no padding. The endpoint reference is useful for developers but is the least essential piece given the surrounding context.

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 two-parameter list tool with no output schema and full schema coverage, the essentials are present, but the description never states what happens on a first call without next_query, what ordering is used, or what a receipt record contains — details an agent needs to interpret results.

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 coverage is 100%: limit bounds and the next_query precedence rule ('other arguments are ignored') are fully documented in the schema. The description's 'Page with next_query' merely echoes that, adding no new semantics, 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?

States a specific verb and resource ('List receipts') and clarifies the scope as receipts of the account, with the printed/digital distinction adding a bit of domain meaning. It does not differentiate from the closest sibling, tillhub_list_transactions, leaving the agent to infer the receipts-vs-transactions boundary.

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 only usage signal is 'Page with next_query', which explains pagination mechanics rather than when to choose this tool. There is no guidance on when to use it instead of tillhub_list_transactions or tillhub_get_transaction, and no prerequisites or exclusions.

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