etsy_receipt_shipments_list

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

Annotations declare readOnlyHint=true, which the description matches. However, the description adds no additional behavioral context, such as pagination behavior, result limits, or ordering. For a list operation, this information is valuable.

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?

At 6 words, the description is extremely short, but it omits crucial usage details. Conciseness should not come at the expense of utility; this is under-specification more than efficient writing.

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 no output schema and no parameter descriptions, the description should explain what the returned list contains (e.g., shipment details). It does not. The tool is simple, but the description lacks completeness regarding results and prerequisites.

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%, and the description does not explain the two required parameters (shop_id, receipt_id). It adds zero meaning beyond the raw schema structure, like what shop_id or receipt_id represent or how to obtain them.

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 'List all shipments for a receipt' uses a specific verb ('List') and identifies the resource ('shipments for a receipt'). It clearly distinguishes from sibling tools like 'etsy_receipt_shipment_create' and 'etsy_receipt_get'.

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 description provides no guidance on when to use this tool versus alternatives, such as when to list shipments vs create a shipment or view receipt details. No contextual hints are given.

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