etsy_receipt_transactions_list

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

The description is consistent with the annotations (readOnlyHint: true), indicating a safe read operation. However, it does not disclose additional behavioral traits such as pagination behavior, rate limiting, or whether the list includes only completed transactions. The annotation already covers safety, so the bar is lower, but the description adds no extra context.

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 a single short sentence, highly concise and front-loaded with the action. It wastes no words, but could include essential details (e.g., 'all transactions for a given shop, with pagination') without significantly increasing length.

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?

Given that the tool has three parameters (one required, two pagination), no output schema, and is a list operation, the description is incomplete. It does not mention pagination behavior, the format of the response, or any filters. The agent lacks key information to use the tool correctly.

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 0%, yet the description fails to explain any of the parameters (shop_id, limit, offset). It does not specify that shop_id identifies the shop, or that limit/offset control pagination. The description adds no value beyond the schema's basic types and constraints.

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 clearly states the action ('List all transactions') and the scope ('for a shop'). It is a specific verb-resource combination that distinguishes it from related tools like etsy_receipt_transaction_get (single transaction) and etsy_receipt_transactions_by_receipt (transactions by receipt). However, 'all' could be ambiguous (all transactions ever in the shop vs. a subset) but is acceptable given the parameter context.

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?

No guidance is provided on when to use this tool versus alternatives such as etsy_receipt_transactions_by_receipt or etsy_receipts_list. There are no usage conditions, prerequisites, or examples. The agent must infer from context alone.

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