etsy_receipt_update

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

With no annotations, the description should disclose behavioral traits of this mutation tool, but it only gives a vague indication of updating. It does not mention if updates are partial or complete, permission requirements, or side effects. 'Update' implies a mutation, but no further details are provided.

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 concise sentence, but it is overly brief for a tool with 5 parameters and no annotations. It could include more information without being verbose.

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, no annotations, and 5 parameters, the description lacks essential context. It does not specify return values, update behavior (e.g., partial update), or how to handle errors. The agent has insufficient 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 coverage is 0%, so the description must compensate. It mentions 'mark as shipped' and 'add a seller note', corresponding to was_shipped and message_from_seller, but does not explain was_paid, shop_id, or receipt_id. The description adds minimal meaning beyond the field names.

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 specifies the verb 'update' and the resource 'receipt', and gives examples like 'mark as shipped, add a seller note'. This clearly communicates the tool's purpose, though it does not differentiate from sibling tools such as etsy_receipt_shipment_create.

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 like etsy_receipt_get or etsy_receipt_shipment_create. It simply states it updates a receipt without context on preconditions or when it's appropriate.

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