etsy_receipts_list

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

The annotation readOnlyHint: true already indicates a read operation. The description adds minimal behavioral context—only that it lists all receipts. It does not mention pagination behavior, rate limits, or what happens if the shop_id is invalid. With annotations handling the read-only status, the description's contribution is low.

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 sentence, very concise. However, it lacks structure and front-loads no critical information beyond the basic purpose. It is concise but at the expense of being minimally helpful.

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 13 parameters, no output schema, and many sibling receipt tools, the description is severely incomplete. It does not explain filtering, pagination, sorting, or return format. The agent cannot effectively use this tool without external knowledge.

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?

The input schema has 13 parameters, yet only 2 have descriptions (max_created, min_created as 'Unix timestamp'), and the description provides no additional meaning for any parameter. The agent has no explanation of what limit, offset, sort_on, or boolean filters do. Schema description coverage is 15%, so the description badly needed to compensate but did not.

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 tool lists all receipts (orders) for a shop, using a specific verb and resource. However, given the many sibling tools related to receipts (e.g., etsy_receipt_get, etsy_receipt_update), the description does not differentiate itself from them.

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 on when to use this tool versus alternatives. For example, there is no mention of pagination parameters (limit, offset) or that this tool returns a list rather than a single receipt. The agent receives no help in deciding between this and other receipt tools.

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